You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We then calls asmcgocall, which switches to g0 before calling the C function
When the signal arrives, sigtramp's getg() gets g0.
In traceback1, even though we have cgoCallers, this check fails because g0.syscallsp is not set (g0.m.curg.syscallsp is set instead), so we don't print the cgo traceback and try to print this as a Go traceback.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, and tip, 1.15, 1.13 (didn't test further back)
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run a program that makes a cgo call which ultimately calls
abort()
.https://play.golang.org/p/eu2cpyzjPyy
(Note that
cgosymbolizer
is not required here, it simply demonstrates that the number still has full information about the crash).What did you expect to see?
Something kind of like this:
What did you see instead?
The text was updated successfully, but these errors were encountered: