Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
runtime: go build panicked with "non-Go code disabled sigaltstack" #16468
Please answer these questions before submitting your issue. Thanks!
1. What version of Go are you using (
It's hard to imagine what the non-Go code is that changed the signal handlers. The obvious answer is the C resolver that the go command is linked against for 'go get'. But this was a 'go build' command, so it shouldn't have been doing any network work at all. Even so the code was there. I tried running a go build github.com/Azure/custom-script-extension-linux/... and send it a SIGWINCH while running and could not reproduce this, neither at tip or at go1.6.
It could be that if there is some C-created thread without a sigaltstack and it takes the signal but runs Go's signal handler. That would crash this way. But I don't see where that C-created thread is coming from in cmd/go.
@ahmetalpbalkan, what version of OS X are you using? Any fancy network firewall or other software?
@rsc this was a pretty standard OS X 10.11 El Capitan setup with go1.6.2 installed via Homebrew. I am now trying to reproduce this on macOS 10.12 Sierra with go1.7.1. It no longer reproduces. It used to repro very easily by splitting iTerm2 windows while
I don't think this issue is important enough to investigate deeper. Closing. Thanks for taking a look.