go: cmd/go: running dsymutil failed: signal: segmentation fault
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version
)?
go version devel +38083c83a6 Thu Dec 7 23:37:46 2017 +0000 darwin/amd64
Does this issue reproduce with the latest release?
No
What operating system and processor architecture are you using (go env
)?
GOARCH=“amd64” GOBIN=“” GOCACHE=“/Users/kevin/Library/Caches/go-build” GOEXE=“” GOHOSTARCH=“amd64” GOHOSTOS=“darwin” GOOS=“darwin” GOPATH=“/Users/kevin” GORACE=“” GOROOT=“/Users/kevin/go” GOTMPDIR=“” GOTOOLDIR=“/Users/kevin/go/pkg/tool/darwin_amd64” GCCGO=“gccgo” CC=“clang” CXX=“clang++” CGO_ENABLED=“1” CGO_CFLAGS=“-g -O2” CGO_CPPFLAGS=“” CGO_CXXFLAGS=“-g -O2” CGO_FFLAGS=“-g -O2” CGO_LDFLAGS=“-g -O2” PKG_CONFIG=“pkg-config” GOGCCFLAGS=“-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/sf/fsn3_vgd0n98r0jb86bgp83r0000gn/T/go-build854984327=/tmp/go-build -gno-record-gcc-switches -fno-common”
Mac Sierra version 10.12.6. Using confluentinc/confluent-kafka-go@99a5addc08f7f0d0c20e51e0746f5af3434a5649.
What did you do?
I tried to compile a program that uses confluent-kafka-go and makes HTTP requests. Unfortunately it’s proprietary, but I can answer questions about it if need be.
I frequently recompile Go tip with the latest commit.
The compilation argument was:
go install -v -race ./...
What did you expect to see?
I expected the program to compile.
What did you see instead?
This error message (and only this error message):
$ go install -v -race ./...
# github.com/proprietary/proprietary/cmd/program
/Users/kevin/go/pkg/tool/darwin_amd64/link: /Users/kevin/go/pkg/tool/darwin_amd64/link: running dsymutil failed: signal: segmentation fault
I can blow away my cache if need be, or try a different commit, but I’m completely in the dark about how to trigger this, and worried that if I make changes (like e.g. blowing away the cache) I won’t be able to reliably reproduce the problem.
Running on my high end Macbook Pro which should have enough memory, CPU etc.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 2
- Comments: 23 (20 by maintainers)
To anybody getting here through a google search, the emergency workaround is stripping the executable
-ldflags=-s
.