Keil Logo

µVISION DEBUGGER: Call Stack+Locals window - no nested functions


Information in this knowledgebase article applies to:

  • µVision Debugger for all 8051, 251, 166, ARM microcontroller architectures

SYMPTOM

The Call Stack + Locals window only shows me the current function including the parameters and local variables, but not the complete call stack of nested functions.

CAUSE

Depending on the toolset, a different level of debug information is available which enables the display of a complete call stack.

  • ARM: The complete call stack including parameters and local variables should be visible in the simulator and the target debugger (ULINK2/ULINKpro/CMSIS-DAP/J-Link etc.).
  • 8051/251/166: Unfortunately, the debug information does not allow the display of the complete call stack with a target debugger (ULINK2, Monitor-51, ISD51, DAS/Miniwiggler, Monitor-166 etc.). Only the current function including parameters and local variables is visible when the target system is stopped and the debugger has access to the memory. In simulation, the complete call stack is available because the simulator tracks all call instructions and the corresponding context.

Depending on the compiler optimization, parameters or local variables which are currently not assigned to a register or to the stack may not visible.

MORE INFORMATION

SEE ALSO

Last Reviewed: Monday, September 26, 2016


Did this article provide the answer you needed?
 
Yes
No
Not Sure
 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.