-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
runtime: crash without a message, potentially in the signal handler #56701
Comments
It's unlikely that the crash is caused by |
CC @golang/runtime |
@mknyszek |
@mknyszek |
|
@cherrymui |
I think this is because the signal handler runs on the signal stack (sigaltstack), not the C stack. From the |
@cherrymui What should I type in gdb to print the signal context? |
I did some tests to observe the core dump caused by C crash.
some output
gdb output
dlv output
output
gdb output
dlv output
It seems that C crashes are extremely difficult to troubleshoot. Although there is some critical information in the output, it cannot be written to the log file(#42888). This result frustrates me.:disappointed: |
Could you please clarify what the precise issue here is? Is the issue the inability to debug this because gdb and delve can't interpret the stack, or is it the occasional crashes your program gets (i.e. do you think these crashes might be a Go issue?)? Both are possible issues, but to move forward on the latter we almost certainly are going to need a reproducer or a core dump to investigate ourselves. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I am running a program using cgo on the centos 7.9-2009 kernel version 3.10.0-1160.71.1.el7.x86_64 machine. This program crashes from time to time. The results of analyzing the core dump file are as follows
Seems to be a crash caused by runtime.usleep ? Please guide me how to proceed
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: