CrossWorks for ARM User Guide

—or—•On the Debug Location tool bar, click the Down One Stack Frame button.—or—•Type Alt++.The debugger moves the cursor to the statement where the call was made. If there is nodebug information for the statement at the call location, CrossStudio opens adisassembly window at the instruction.Setting a breakpoint on a return to a functionTo set a breakpoint on return to a function, do one of the following:•In the Call Stack window, click the stack frame on the function to stop at when itis returned to.•From the Build tool bar, click the Toggle Breakpoint button.—or—•In the Call Stack window, click the stack frame on the function to stop at when itis returned to.•Type F9.—or—•In the Call Stack window, right click the function to stop at when it is returned to.•From the popup menu, click Toggle Breakpoint.Execution counts windowThe Execution Counts window shows a list of source locations and the number of timesthose source locations have been executed. This window is only available for targetsthat support the collection of jump trace information.The count value displayed is the number of times the first instruction of the sourcecode location has been executed. The source locations displayed are target dependent- they could represent each statement of the program or each jump target of theprogram. If however the debugger is in intermixed or disassembly mode then thecount values will be displayed on a per instruction basis.The execution counts window is updated each time your program stops and thewindow is visible so if you have this window displayed then single stepping may beslower than usual.Chapter 12Execution counts window111