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 Commands
Debug Manual—421921-003
4-52
I Command
Considerations
The HELP command is not available if the priority of the process being debugged is
greater than or equal to the priority of the memory manager.
I Command
The I command displays instruction code. The default instruction set depends on the
process type, but the instruction set can be specified by the mode parameter. The
display syntax of this command is as follows:
address
is the address of the first variable to be displayed. For more information, see
Address Syntax on page 3-12.
length
specifies the number of instructions to be displayed by Debug.
[OUT] output-dev
specifies where the display is directed. Debug output can be directed to an output
device, a process, or a spooler collector. Debug output cannot be directed to a disk
file. If you omit output-dev, Debug assumes the home terminal.
The output-dev parameter has these formats.
Syntax for a device other than a disk:
[ node.]{device-name[.qualifier ] }
{ldev-number }
Syntax for a named process:
[ node.]process-name[:seq-no][.qual-1[.qual-2] ]
Syntax for an unnamed process:
[ node.]$:cpu:pin:seq-no
For syntax descriptions of these process and device names, see the Guardian
Procedure Calls Reference Manual.
mode
specifies the instruction set options. The mode parameter has this format:
{ T | N | R }
I address [ , length ]
[ , [ OUT ] output-dev ] [ : mode ]