Just to confirm, this indeed fixed things. Thanks for the quick response!
On Mon, Jan 15, 2018 at 2:31 PM, James Waldrop wrote:
> Aha, I did. I was cross compiling. Thank you!
>
> On Mon, Jan 15, 2018 at 2:27 PM Ian Lance Taylor wrote:
>
>> On Mon, Jan 15, 2018 at 1:43 PM, wrote:
>> >
>> > My
Aha, I did. I was cross compiling. Thank you!
On Mon, Jan 15, 2018 at 2:27 PM Ian Lance Taylor wrote:
> On Mon, Jan 15, 2018 at 1:43 PM, wrote:
> >
> > My bootstrap Go is a 1.9.2 binary, and I'm trying to compile Go on High
> > Sierra (MacOS 10.13.2).
> >
> > I get a SIGSEGV during test run:
>
On Mon, Jan 15, 2018 at 1:43 PM, wrote:
>
> My bootstrap Go is a 1.9.2 binary, and I'm trying to compile Go on High
> Sierra (MacOS 10.13.2).
>
> I get a SIGSEGV during test run:
>
> # cmd/go terminal test
> panic: runtime error: invalid memory address or nil pointer dereference
> [signal SIG
My bootstrap Go is a 1.9.2 binary, and I'm trying to compile Go on High
Sierra (MacOS 10.13.2).
I get a SIGSEGV during test run:
# cmd/go terminal test
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x110ed
