Closed
Description
What version of Go are you using (go version
)?
$ go version go version devel +acf3ff2e8a Tue Dec 3 17:35:06 2019 +0000 linux/arm64
Does this issue reproduce with the latest release?
Reproducible with the tip.
What operating system and processor architecture are you using (go env
)?
go env
Output
$ go env GO111MODULE="" GOARCH="arm64" GOBIN="" GOCACHE="/home/xiaji01/.cache/go-build" GOENV="/home/xiaji01/.config/go/env" GOEXE="" GOFLAGS="" GOHOSTARCH="arm64" GOHOSTOS="linux" GOINSECURE="" GONOPROXY="" GONOSUMDB="" GOOS="linux" GOPATH="/home/xiaji01/.go" GOPRIVATE="" GOPROXY="https://proxy.golang.org,direct" GOROOT="/home/xiaji01/util/go" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/home/xiaji01/util/go/pkg/tool/linux_arm64" GCCGO="gccgo" AR="ar" CC="gcc" CXX="g++" CGO_ENABLED="1" GOMOD="/home/xiaji01/util/go.dbg2/src/go.mod" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build624397069=/tmp/go-build -gno-record-gcc-switches"
What did you do?
cd /src
GO_GCFLAGS='-N -l' ./all.bash
What did you expect to see?
building passes.
What did you see instead?
Testing of runtime package failed:
fatal error: traceback_arm: found jmpdefer when tracing with callback
It turns out TestCallersDeferNilFuncPanic triggers the error in function 'gentraceback', so far I could reproduce the issue with running './all.bash' only, both 'go test ...' and 'go tool dist test' works fine.
My questions:
- Does building Go with '-N -l' options make any sense?
- Any better way to debug such issues?
Thanks a lot.