Debugging Commands

The table below summarizes the behavior of the debugging commands available in NextGen TotalView for HPC. The descriptions assume that the command is being applied to a single thread, the thread with the focus. In fact, debugging commands are much more flexible than this. They can apply to threads, processes, or groups, or some collection of these. You select the different scopes for debugging commands from the menu on the left of the toolbar, or by selecting the commands from the Thread, Process, and Group menus.

Command	Description
Go	Sets the thread to running until it reaches a stopping point. Often this will be a breakpoint that you have set, but the thread could stop for other reasons.
Halt	Stops the thread at its current execution point.
Kill	Stops program execution. Existing breakpoints and other settings remain in effect.
Restart	Stops program execution and restarts the program from the beginning. Existing breakpoints and other settings remain in effect. This is the same as clicking Kill followed by Go.
Next	Moves the thread to the next line of execution. If the line the thread was on includes one or more function calls, NextGen TotalView for HPC does not step into these functions but just executes them and returns.
Step	Like Next, except that NextGen TotalView for HPC does step into any function calls, so the thread stops at the first line of execution of the first function call.
Out	If the thread is in a block of execution, runs the thread to the first line of execution beyond that block.
Run To	If there is a code line selected in one of the Source views, the thread will stop at this line, assuming of course that it ever makes it there. This operates like a one-time, temporary breakpoint.

RELATED TOPICS
Controlling the scope (width) of debugging commands	"Debugging Command Width"
Controlling what happens when a thread reaches a breakpoint (action point)	"Controlling an Action Point’s Width"
Seeing the debugging commands in action	"Stepping and Executing"