STM32: Debugger doesn't jump to code location via "Step into"
Hi,
I have a strange problem for one week, when I returned to working on my code again:
In Debug mode for some cpp files the debugger isn't generating breakpoint markers in these files/functions and I'm only able to step through the disassembled code as in my screenshots.
I don't know if I accidentally changed important settings, but with the same code I didn't have this problem before.
I changed optimization and debugging levels back and forth but no change.
Can you help me?
Regards,
Johannes
-
No, unfortunately all have the same properties. Debug Level 2 and Optimizatzion Level is debug for these files.
In another community thread I asked, if I can reset the properties for tagged files with "modified properties", but couldn't figure out what the user meant with his response.
-
Hi Jon,
The first function is in a file called control.cpp inside the misc folder. In this function there are other calls of functions from Pushbutton.cpp and LED.cpp.
For checking, I set up a completely new project with identical folder structure and only matched the following properties from the not working project: Debug Level, Code Optimization, Include Directories and the c Language level
And with this, the debugger behaviour is as expected.
Update:
I finally found the issue. Somehow I had the debugging level set to NONE in the "Thumb Debug" accidentally, and only changed the "Common" setting for the debug information.
Also I was wondering, if I change for example the debug level in the private debug configuration, it doesn't inherit this setting into the Thumb Debug. So which configuration is the source for each public configuration's inheritance?
Unfortunately, I can't upload files here, because I would like to upload both project files, so you could check the differences.
Please sign in to leave a comment.
Comments
4 comments