Debug Manual

Introduction
Debug Manual—421921-003
1-14
Necessary Compiler Listing
Example:
RUND \sysb.$vol3.subv4.oprog / NAME $pro1 /
To debug remotely, you use the same commands discussed under How to Make a
Process Enter Debug on page 1-2. Specifically, the commands and procedures are:
Necessary Compiler Listing
To debug a program, you need a compiler listing of the program. As your
source-language compiler permits, you should specify these compiler directives:
Programmers familiar with the machine instructions might find a listing of the
instruction codes helpful. These source-language compiler directives enable the listing
of instruction codes:
How Debug Breakpoints Work
A breakpoint is a location (or “point”) in your program where you want to suspend
execution so that you can then examine and perhaps modify the program’s state.
Example of a Code Breakpoint
For a code breakpoint, you specify a location in the code area where you want the
process to enter the debug state just before execution of that code. The operating
Figure 1-2. Debugging a Remote Process
Commands RUND and DEBUG entered from the command interpreter
Procedures PROCESS_LAUNCH_, PROCESS_DEBUG_, and
DEBUGPROCESS
?LIST Lists the source program and enables other listings
?MAP Specifies maps of the identifiers used in the source program
?LMAP* Specifies a map of procedure entry points
?CODE Lists instruction codes in octal for entire procedures
?ICODE Lists instruction code mnemonics for entire procedures
?INNERLIST Lists instruction code after each statement
VST0102.vsd
$PRO1
Home
Terminal
$HT
\SYSA \SYSB