Debug Manual

Debug Manual—421921-003
3-1
3
Debug Command Overview
This section introduces all of the Debug commands (by functional groups), explains the
structure of the commands, and shows the primary relationships between the
commands. For more information on how to use the Debug commands, see Section 4,
Debug Commands
Types of Debug Commands
The commands in Table 3-2 through 3-7 are grouped according to the various types of
Debug commands:
•
Breakpoint Commands
•
Display Commands on page 3-3
•
Modify Commands on page 3-4
•
Environment Commands on page 3-5
•
Privileged Commands on page 3-5
•
Miscellaneous Commands on page 3-6
This grouping is useful in that it indicates some of the relationships between the
commands. For example, the code breakpoint commands consist of the B and C
commands. The B command sets code breakpoints, and the C command clears them.
Breakpoint Commands
There are two subgroups of breakpoint commands: code and memory-access.
Table 3-1 on page 3-2 gives an overview of these commands.
A code breakpoint is a designated location in the code area that, when executed,
causes the process to enter the debug state. The code breakpoint commands consist
of the B and C commands.
A memory-access breakpoint is a designated location in memory that, when accessed
in the specified way (read, write, write/read, or change), causes the process to enter
the debug state. The operating system allows only one memory-access breakpoint for
each process. The memory-access breakpoint commands consist of the BM and CM
commands.