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-7
Capitalization in Commands
Capitalization in Commands
Note that uppercase and lowercase letters are interchangeable in Debug commands.
The syntax shows keywords in uppercase letters.
Default Commands
Certain Debug commands have defaults. A default for a command is a variant of the
command that is executed when you simply press RETURN at the Debug prompt
without actually entering the command. Default commands are valid only when certain
conditions exist. Whenever a default command would be a valid entry, the command
name appears in the Debug prompt. For example:
251,06,00024 (FN)-
This prompt signifies that if you press RETURN, the default version of the FN
command is executed. Note that you can also enter other commands when Debug
displays this prompt.
More information about default commands is given in the descriptions of the
commands that have defaults.
Table 3-1 on page 3-2 through Table 3-5 on page 3-5, list the function or functions of
each command and give a brief description of each function.
Notation for Privileged Commands
Underlined keywords or characters in command syntax are available to privileged
users only. Keywords or characters that are not underlined are available to both
privileged and nonprivileged users.
Register Syntax
Several Debug commands have register names as parameters or registers specified in
expressions. The form of a register specification is:
register
represents the contents of a processor register for that process. It can be either a
TNS/R register or a TNS environment register.
A TNS/R register is one of the following:
{ $00 | $01 | ... | $31 }
{ $HI | $LO }
{ $PC }
{ $F00 | $F01 | ... | $F31 }
{ $FCR31 }