-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: fatal error: unknown caller pc #44503
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
That stack frame does look pretty trashed. Not sure how that would happen. Does it still fail with 1.16? @mdempsky Might be a libfuzzer issue. |
I won't rule out libfuzzer, but I don't immediately see anything that libfuzzer is doing wrong. The compiler instrumentation is fairly simple (just inserting some global counter increments, or calls to runtime helpers), and the runtime helper code (runtime/libfuzzer.go, runtime/libfuzzer_{amd,arm}64.s) doesn't appear to have diverged any from the race-detector code it was based on. (At least for Go 1.16; I do see a few dev.regabi-related CLs that only updated race_amd64.s, but not libfuzzer_amd64.s; /cc @cherrymui.) It could maybe be related to the open-coded defer issues (#43882, etc; /cc @danscales)? Those failures sometimes manifested as "unknown caller pc" crashes. If so, it would be helpful to know if the issue still reproduces with Go 1.16, since that release includes fixes for the cases that are known to affect end user code (a5a5e2c). |
That code should only have effect if GOEXPERIMENT=regabi is enabled (of course there could be bugs in the changes). I may need to update libfuzzer_amd64.s, at some point. Thanks for bringing this up. |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Not sure, we don't control this (oss-fuzz)
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
No crash
What did you see instead?
Crash
The text was updated successfully, but these errors were encountered: