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
Truncated call stack #306
Comments
Getting 20 at a time is the default in VSCode. There should be a UI element to get more. Can you attach a screenshot if the call-stack window at the bottom? |
VSCode initially had a hardcoded limit of 20 frames. After many complaints, looks like they fixed it. However, we were not aware they fixed it and we have to tell VSCode that "we can get more frames if it wants". You will now see the following in the Call Stack Window if there are more frames available The way VSCode UI was designed, it will only load 20 additional frames. Not in our control. I prepared you a preview release so you can verify with Rust. Especially for accuracy. https://github.com/haneefdm/cortex-debug/releases/tag/v0.3.7-pre4 |
Wow that was fast, thank you! The preview works perfectly. |
I am hoping to make a release this weekend. Enjoy |
Hi!
I'm debugging a Rust application running on an nRF52 (cortex-m4-r0p1) using a j-link probe and j-link server.
Most of the time the debugging experience is fine. However, my callstack seems to be truncated to 20 or so elements, even when
backtrace
in debug console lists 51.The text was updated successfully, but these errors were encountered: