[go-nuts] Re: SIGSEGV in io.copyBuffer

2019-07-30 Thread Antony Rheneus
nvalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x66180] goroutine 11fatal error: [malloc deadlock , panic during panic [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x66180] 108033889401^Ifatal error: unexpected signal durin

[go-nuts] Re: SIGSEGV in io.copyBuffer

2019-07-30 Thread Antony Rheneus
Please dont jump into conclusion on qemu. -Antony On Tuesday, July 30, 2019 at 6:15:43 PM UTC+5:30, Antony Rheneus wrote: > > > Seeing segfault during go get -v URL > > > > $ go version > go version go1.11.5 linux/arm > > > > $ go env > GOARCH="arm&qu

[go-nuts] SIGSEGV in io.copyBuffer

2019-07-30 Thread antony . rheneus
Seeing segfault during go get -v URL $ go version go version go1.11.5 linux/arm $ go env GOARCH="arm" GOBIN="" GOCACHE="/var/arheneus/.cache/go-build" GOEXE="" GOFLAGS="" GOHOSTARCH="arm" GOHOSTOS="linux" GOOS="linux" GOPATH="/var/arheneus/go" GOPROXY="" GORACE="" GOROOT="/usr/local/go"