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
Received panic throw("signal_recv: inconsistent state") on Mac while debugging #42619
Comments
Thank you for raising this issue. Before we can investigate further you will need to provide us with instructions for how to reproduce the issue. If you can provide a program which demonstrates the issue that would be ideal. |
here? |
Unfortunately, the code it happened in is closed source. If I'm able to reproduce it again I'll try to create an example. |
@calbot I understand. It's going to be tricky to debug this without a way to reproduce it. In the interim, would you please make sure that you code passes all tests under the race detector, and deploy a race enable version to your production traffic to verify that there are no data races in you program. Thank you |
This happens to me somewhat often too. Proprietary code also sadly, and I wasn't able to reproduce it yet standalone. One trigger seems to be changing breakpoints while a debugged Go program is still running under Vs Code with vscode-go. I think it sends a |
I did have a data race. I'll see if the problem still happens now that I've fixed that. |
Glad you found it. Please be sure to close this issue when you’ve confirmed the issue is gone. |
Caused by a data race, closing. |
What operating system and processor architecture are you using (
go env
)?go env
OutputReceived
throw("signal_recv: inconsistent state")
runtime.fatalthrow (/usr/local/go/src/runtime/panic.go:1162)
runtime.throw (/usr/local/go/src/runtime/panic.go:1116)
os/signal.signal_recv (/usr/local/go/src/runtime/sigqueue.go:140)
os/signal.loop (/usr/local/go/src/os/signal/signal_unix.go:23)
runtime.goexit (/usr/local/go/src/runtime/asm_amd64.s:1374)
Not very consistently reproducible. I've had it happen a handful of times.
It doesn't look like this should be possible given how that sig.state is only changed with atomic functions.
I'm using github.com/panjf2000/gnet which uses kqueues. I'm not sure if that could be part of the problem somehow.
The text was updated successfully, but these errors were encountered: