Related Topics:
Related Topics:| Moving Around the Call Stack | Redisplaying the Stopped in Function |
| Redisplaying the Context Function | Popping the Call Stack to the Current Frame |
| Turning Off Verbose Stack Information. |
The call stack represents all currently active routines -- those that have been called but have not yet returned to their respective caller. In the stack, the functions and their arguments are listed in the order in which they were called. The initial function, main() for C and C++ program, is at the top of the Stack pane; the function executing when the program stopped is at the bottom of the Stack pane. This function is known as the stopped in function.
The stopped in function is listed in the Stopped In status line. The source code of the stopped in function is displayed in the editor window. The next line to be executed is highlighted in green.
The Evaluation Context line in the status area provides the name of the context function, which determines the scope-resolution search order that applies when you provide a symbol name in various debugging operations. In the call stack, a purple arrow points at the context function if it differs from the stopped in function. Knowing the context function is important when evaluating expressions, displaying data, and setting breakpoints.
You can move through the call stack using the Up or Down buttons or by clicking the function name. When you move to a new stack frame, that frame becomes the context function. The stopped in function does not change.
If the source code for the context function is available, it is displayed in the editor window. The next line of source code to be executed in that function is highlighted in purple.
Verbose stack information causes more symbolic information to be loaded increasing the memory footprint. You can increase performance speed and save RAM and swap space by turning off verbose stack information.
The call stack viewer normally shows the full call signature. If you want to conserve space, you can show only the function names by turning off verbose stack information.