-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/debug/cmd/viewcore: viewcore panics: bad int32 type uint32 #45984
Comments
/cc @hyangah @randall77 |
This happens even with a trivial program, which I should have checked first.
If I run this with
|
The problem here seems to be that the types of Fixing that locally seems to improve matters! But, there are still some things broken even after patching
Some cores give messages like this:
Some cores fail to load altogether:
I'm wondering, perhaps there are some more updates that need to be applied for a more recent version of Go here? |
I have submitted a PR to fix this problem and another. Please take a look: golang/debug#7 |
Should this be closed, then? |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I attempted to use
viewcore
on a core dump from CockroachDB. I ran the CockroachDB binary, killed it withSIGSEGV
, and collected the resultant dump. Then, I ranviewcore
with theoverview
argument.What did you expect to see?
Viewcore output, which could hopefully help me track down some issues with memory usage. 😄
What did you see instead?
A panic:
Here is a link to the core dump (334 MB): https://drive.google.com/file/d/1KlwSvP-5xxghBRHprxsmtFFQtsK9zAmg/view?usp=sharing
Here is a link to the binary used (178 MB): https://drive.google.com/file/d/147h4wTi7WloFWPjIXm4kZoIGPNvu6QNz/view?usp=sharing
I know this is a bit of a heavy repro, but I'm not quite sure how else to track down the issue. Any ideas would be appreciated for how to produce a smaller case for you to look at.
@randall77, would you have an idea about this issue? I saw #38638, but this appears to be a different issue.
Thank you!
The text was updated successfully, but these errors were encountered: