Debug Manual
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- Execution Modes on TNS/R Systems
- What User Access Is Required for Debugging
- How to Make a Process Enter Debug
- How to Select Debug as the Debugger
- Why a Process Enters Debug
- How to Determine Process State on a Trap or Signal
- Ending a Debug Session
- What Appears in the Debug Header Message
- How to Use Debug
- How Debug Breakpoints Work
- 2 Using Debug on TNS/R Processors
- 3 Debug Command Overview
- 4 Debug Commands
- Command Summary
- A Command
- AMAP Command
- B Command
- BASE Command
- BM Command
- C Command
- CM Command
- D Command
- DJ Command
- DN Command
- EX[IT] Command
- F[ILES] Command
- FC Command
- FN Command
- FNL Command
- FREEZE Command
- HALT Command
- H[ELP] Command
- I Command
- IH Command (TNS/R Native and OSS Processes)
- INSPECT Command
- LMAP Command
- M Command
- MH Command (TNS/R Native and OSS Processes)
- P[AUSE] Command
- PMAP Command (Accelerated Programs)
- PRV Command
- R Command
- S[TOP] Command
- T Command
- V Command
- VQ Command
- VQA Command
- = Command
- ? Command
- A Error Messages
- B ASCII Character Set
- C Command Syntax Summary
- Register Syntax
- Expression Syntax
- Address Syntax
- A Command
- AMAP Command
- B Command
- BASE Command
- BM Command
- C Command
- CM Command
- D Command
- DJ Command
- DN Command
- EX[IT] Command
- F[ILES] Command
- FC Command
- FN Command
- FNL Command
- FREEZE Command
- HALT Command
- H[ELP] Command
- I Command
- IH Command
- INSPECT Command
- LMAP Command
- M Command
- MH Command
- Output-Device Syntax
- P[AUSE] Command
- PMAP Command
- PRV Command
- R Command
- S[TOP] Command
- T Command
- V Command
- VQ Command
- VQA Command
- = Command
- ? Command
- D Session Boundaries
- E Correspondence Between Debug and Inspect Commands
- F Sample Debug Sessions
- Glossary
- Index

Debug Command Overview
Debug Manual—421921-003
3-6
Miscellaneous Commands
Miscellaneous Commands
Miscellaneous Debug commands are listed in Table 3-6.
Multiple Commands on a Line
Debug allows multiple commands on a line, each separated by a semicolon (;). This
feature allows you to enter very sophisticated and powerful command lines while
debugging.
Command Structure
Most of the Debug commands have one function and one syntax definition. However,
the A, B, BM, D, and M commands have more than one function. For these
commands, each function has its own definition and its own syntax.
For example, the B command has five functions: set unconditional code breakpoint, set
conditional code breakpoint, set trace code breakpoint, set execute code breakpoint,
and display code and memory-access breakpoints. Although all of these functions deal
with setting breakpoints, each function has a unique description and a unique syntax.
PRV Privileged Enables or disables the use of privileged commands.
V Vector Allows access to other address spaces.
VQA Vector Sets the current selectable data segment to the specified
absolute segment numbe
r.
Table 3-6. Process Control Commands
Command Meaning Description
FC Fix
command
Fix Debug command. Allows you to edit the last Debug
command that you entered.
EX[IT] Exit Exits the Debug session.
H[ELP] Help Displays requested help information about a Debug command,
variable, or all help topics.
INSPECT Run
Inspect
Switches to the Inspect debugger.
P[AUSE] Pause Pauses (suspends) the process for a specified time.
R Resume Resumes program execution (leaves the debug state).
S[TOP] Stop Stops process execution.
Table 3-5. Privileged Commands (page 2 of 2)
Command Meaning Description