-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: fatal error: invalid runtime symbol table (not able to reproduce) #30092
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 @randall77 @aclements |
Strange. It is complaining that it's trying to find out how big the stack frame is for the function The weird part is that I don't see that function in the tracebacks anywhere. So why is the runtime asking about it? How is it getting that pc, given that it couldn't possibly be the pc of an instruction actually executed by the program? There's some additional sigtramp nonsense in there which may be obscuring the part of the stack trace that contains the mentioned function. Could you verify that in your executable, address 0x7b6b06 is in that function mentioned above, and that it is junk? It should look like this:
If you could paste in the issue the actual disassembly around 7b6b06 that would help. Even if that checks out, I'm not sure what to do about it. It seems like the pc got corrupted somehow. |
(edited above as I accidentally ran it on macos instead of the original linux env) I can confirm that the function header is |
Thanks for all the info. |
@randall77 no worries, I figured it was worth posting, just in case it was useful. Feel free to close it unless you want to keep it open for reference. |
Closing since the data is insufficient. Please feel free to reopen if you are able to reproduce this. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
I have not been able to reproduce the issue. The dataset is much too large, and code far too complex to determine the trigger.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I ran a newly compiled version of my program, and it crashed. The changes I had made had not yet been reached during operation of the program, it was still in a "bootstrapping" phase of loading in data.
GOGC
was set to50
.GODEBUG
was set togctrace=1
What did you expect to see?
Normal execution.
What did you see instead?
The text was updated successfully, but these errors were encountered: