RealView Debugger User Guide - ARM Information Center

Working with Debug Views6.4 Using the call stackProcessors maintain a call stack for each processor in your debug target. If you aredebugging multithreaded applications, a thread stack is also maintained.As a program function is called, it is added to the call stack. Similarly, as a functioncompletes execution and returns control normally, it is removed from the call stack. Thecall stack, therefore, contains details of all functions that have been called but have notyet completed execution.RealView Debugger includes features that enable you to monitor variables and accesstraceback as your debugging session develops:• Using the Stack pane• Using the Call Stack pane.6.4.1 Using the Stack paneThe Stack pane enables you to monitor activity on the stack during program executionby giving access to the stack as raw memory. See Working with the stack on page 6-30for full details.6.4.2 Using the Call Stack paneUse the Call Stack pane to follow the flow of your application through the hierarchicalstructure by examining the current status of functions and variables. This enables youto see the path that leads from the main entry point to the currently executing functionat the top of the stack. You can also use the Call Stack pane to set breakpoints.The Call Stack pane shows the:• name of the function• line number in the source file from which the function was called• parameters to the function.To use traceback:1. Select Target → Reload Image to Target to reload the image dhrystone.axf.2. Click on the Src tab to view the source file dhry_1.c.3. Set an unconditional software breakpoint by double-clicking on line 301.4. Click Run to start execution.5. Enter 5000 when asked for the number of runs.6-36 Copyright © 2002-2005 ARM Limited. All rights reserved. ARM DUI 0153G