-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
debug/dwarf: r.Next() returns wrong ent when DWARF5 used. #57046
Comments
Can you make the test file available somewhere? Or provide a standalone test? Thanks. CC @thanm @aclements |
vmlinux is too big to share.
|
Test program
|
Attach the init/main.o instead https://github.com/joeyjiaojg/go/raw/master/test/dwarf/dwarf5.o |
It's going to be difficult for us to fix this problem if we can't recreate it ourselves. Anything you can do to make that possible would be appreciated. Thanks. |
you can reproduce
|
To avoid confusion, you can use the test steps below only:
|
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.) |
Reopening because @joeyjiaojg provided repro instructions. |
What version of Go are you using (
go version
)?go 1.19.3
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?What did you do?
Above is extracted from vmlinux (compiled by clang-15) by llvm-dwarfdump-15, when linux kernel compiled with DWARF5 debug info, go debug/dwarf can't decode entry at 0x000160e6 correctly.
Test program
What did you expect to see?
The 2nd printf should print ent name as rcu_read_unlock.
What did you see instead?
The 2nd printf should print ent name of some other subprogram.
The text was updated successfully, but these errors were encountered: