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-17
Display Breakpoints
Format of the Code Breakpoint Display
Debug displays TNS and native code breakpoints in this form:
TNS code breakpoint:
Native code breakpoint:
[@ | >] code-segment, addr-16 INS: instr SEG:memory-seg
[PIN: { <pin-num> | ALL }
]
INS: mnemonic-instr
[ condition ]
[ trace ]
[ command-string ]
[^--] N: addr-32 INS: instr-32
INS: mnemonic-instr-32
[ condition ]
[ trace ]
[ command-string ]
> (greater-than sign) denotes a memory-exact point, for
accelerated programs only.
@ (commercial at sign) denotes a register-exact point, for
accelerated programs only.
code-segment defines the TNS code segment where the breakpoint is set.
Segments are:
UC.segment-num ! in user code space
UL.segment-num ! in user library space
SC.segment-num ! in system code space (privileged only)
SL.segment-num ! in system library space (privileged only)
Characters appearing in the display before UC, UL, SC, or SL
indicate that the breakpoint is set on corresponding TNS and
RISC instructions as follows:
addr-16 is the 16-bit word address where the breakpoint is set. This
address is within the specified code segment.
instr is the octal value of the instruction at the address defined by
code-segment, addr-16. This value is the value of the
instruction at the time the breakpoint was set. While the
breakpoint is set, the content of code-segment, addr-16 is a
BPT (TNS) instruction (000451).
SEG is the segment in memory where the breakpoint is set.
memory-seg the memory segment.