The CLI lets you start debugging operations in several ways. To execute your program from within the CLI, enter a dload command followed by the drun command.
If your program is launched from a starter program such as srun or yod, use the drerun command rather than drun to start your program. If you use drun, default arguments to the process are suppressed; drerun passes them on.
The following example uses the totalviewcli command to start the CLI. This is followed by dload and drun commands. Since this was not the first time the file was run, breakpoints exist from a previous session.
In this listing, the CLI prompt is “d1.<>”. The information preceding the greater-than symbol (>) symbol indicates the processes and threads upon which the current command acts. The prompt is discussed in About the CLI Prompt.
% totalviewcli
d1.<> dload arraysAlpha #load the arraysAlpha program
This two-step operation of loading and running supports setting action points before execution begins, as well as executing a program more than once. At a later time, you can use drerun to restart your program, perhaps sending it new arguments. In contrast, reentering the dload command reloads the program into memory (for example, after editing and recompiling the program).
The dload command always creates a new process. The new process is in addition to any existing processes for the program because the CLI does not shut down older processes when starting the new one.
The dkill command terminates one or more processes of a program started by using a dload, drun, or drerun command. The following example continues where the previous example left off:
Because information is interleaved, you may not realize that the prompt has re-appeared. It is always safe to use the Enter key to have the CLI redisplay its prompt. If a prompt isn’t displayed after you press Enter, you know that the CLI is still executing.