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
cmd/compile: keep variable declaration order in debug_info #31133
Comments
The issue is labeled debug/dwarf, but are you asking for a change in the debug/dwarf package or a change in the compiler? |
it's a change to the compiler, it should be labeled cmd/compile. |
Updated, sorry, I don't particularly know these areas. Thank you for the heads-up. |
/cc @randall77 |
I'll give this a look. |
There's no test that verifies what you'd hope to be looking for, is there? And is the intended outcome "better debugging, once the debuggers are adapted to this change"? I thought I found the offending sort yesterday in an old CL, but it appears to have been moved since then. |
Change https://golang.org/cl/173439 mentions this issue: |
Rather than adding
DeclColumn
info todebug_info
, it would be great to write the variables in the declaration order. This would make it easier to display the variables in a predictable and consistent order while debugging and thus better align with the source code presentation.The text was updated successfully, but these errors were encountered: