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
Static variables don't show #929
Comments
Thank you for reporting this issue. And, thank you for doing the detective work. A LOT has changed even since March. It appears that we created an invalid name for a gdb variable (the quotes and the backslashes). A fix is on the way... |
Could you try the latest pre-release and let me know? https://github.com/Marus/cortex-debug/releases FYI: We had to prefix statics with file name because disambiguate files have the same name statics. With C++ and auto-generated code, it is becoming fairly common to have name collisions. This was a Windows only problem/fix. Stupid backslashes. Again, thank you for reporting this. If this checks out okay, you can expect a new release within days. |
I don't have hardware to test right now, but it looks good now. (Or is there a way to test without hardware?) Glad to help out. It started to annoy me, so I kept digging and this is where I came out. I would have fixed it myself, but I didn't know what thoughts went into how exactly the variable should be named. I can test it again on Monday or Tuesday |
I tested it today and it works now! |
Describe the bug
When debugging an ARM executable, the static variable section in the variable pane always stays empty, even if there are static variables in the source file.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Static variables should show up
Screenshots
Environment:
Please include
launch.json
Attach text from
Debug Console
Additional context
I did a bisect and the first bad commit is 2f07c52
I looked at the source code and it seems the issue is in gdb.ts staticVariablesRequest(). Here the exprName which is passed to gdb is prefixed with the filename. This causes the gdb server to throw an error.
The text was updated successfully, but these errors were encountered: