The Debug view displays the call stack entry for the suspended threads for each target you are debugging. Each thread in your program appears as a node in the tree. The thread at the current execution point automatically expands. If the thread is suspended, its node is expanded to show its call stack entry.
A thread's call stack entries are only valid when the thread is stopped or suspended. In particular, if you use the i Job launch configuration to debug a service program and then start the debug session by calling a program, the call stack will not be updated when you step over the end of the calling program. To see the updated call stack, issue a halt or suspend action. For information about using the i Job launch configuration, see the full prompt job debugging topic below. For information about halting, see the related topic below.
If the resource containing a selected thread is not open and/or active, the file opens in the editor and becomes active, focusing on the source with which the thread is associated and highlighting the source line that the program is about to execute.
In the Debug view, you can perform various start, step, and terminate debug actions.
To view stack information, click on the Debug view to bring it in focus, and expand the appropriate thread entry. Right-click on the call stack entry that you want to view and select Properties from the pop-up menu. Alternatively, you can have detailed properties of stacks displayed in the Properties view, as follows:
Nodes in the Debug view are visible if they are at the top level of the tree structure, or if the nodes a level higher have been expanded. For all nodes that are visible in this view, you can jump to a specific node by typing the first letter of the node. The view will jump to the next node that begins with that letter. If this node is not the node that you wanted to jump to, type the first letter again to jump to the next node that begins with the letter, and so on.