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
Introduction
Debug Manual—421921-003
1-11
Header Message Format
The elements reported in the Debug header message are explained as follows:
P-register is the 16-bit octal current value (P register) of the program
counter for TNS or accelerated mode. Typically, this is where a
breakpoint was specified.
32-bit-
address
is the 32-bit hexadecimal current value (PC register) of the
program counter for native mode. Typically, this is where a
breakpoint was specified.
ENV-register is the current value in octal of the TNS environment ENV
register. For more information on register field descriptions, see
Figure 1-1 on page 1-9. In native mode, only the PRIV and DS
fields are valid.
space-
identifier
is one of these values:
UCr
SRL
SCr
SLr
UC.segment-num
UL.segment-num
SC.segment-num
SL.segment-num
The space-identifier defines the current code segment. UC
indicates that the code segment is within the user code space.
Within a user code space there can be up to 32 segments of
code.
SRL indicates that the code is within one of the TNS/R native
shared run-time library code spaces.
SC indicates that the code segment is within the system code
space. SL indicates that the code segment is within the system
library space.
An r indicates that the segment is within the code space for
native object code. (UC with no r and no segment-num appears
in some displays and is equivalent to UCr.) For a process in TNS
or accelerated mode, the segment-num appears instead of an r
and defines the particular code segment. SRL always refers to a
space for native object code.
For more information about space identifiers, see the server
description manual appropriate for your system.
[ info ] is the header message; it is described in the next subsection.