-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: go build panicked with "non-Go code disabled sigaltstack" #16468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
/cc @ianlancetaylor |
The signal is |
@ianlancetaylor yes, I was running iTerm2 and just hit Cmd+D which would split my terminal emulator window horizontally into two. This effectively shrinks my current terminal window where the |
I just ran into this too, with go |
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. |
Please answer these questions before submitting your issue. Thanks!
1. What version of Go are you using (
go version
)?2. What operating system and processor architecture are you using (
go env
)?3. What did you do?
First of all I was not able to reproduce this error ever again It was an one-off thing and when I googled the error only the source code came up, so reporting.
It occurred when I was doing
go build
on(&to) darwin/amd64.4. What did you expect to see?
go build
to work.5. What did you see instead?
The text was updated successfully, but these errors were encountered: