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-5
Environment Commands
Environment Commands
The environment commands are listed in Table 3-4.
Privileged Commands
Table 3-5 contains commands for privileged users only. Privileged commands are
those permitted only if they have been enabled by use of the PRV ON command. To
successfully issue the PRV ON command, the process being debugged must be
executing under the local super ID. (Privileged debugging is distinct from the privileged
state of process execution, which permits a process to perform privileged operations
that are normally permitted only to the operating system.)
The privileged commands include those that have address parameters to:
•
Access data and code in the kernel address space.
•
Plant code breakpoints in code containing PRIV or CALLABLE procedures,
including licensed UC, UL, UCr, SRLs, or system code and library.
•
Modify code.
Table 3-4. Debug Environment Commands
Command Meaning Function Description
BASE Numeric
base
Set numeric base Sets numeric base for input to Debug,
output displays by Debug, or both.
VQ Vector Q
segment
Change selectable
segment
Changes the selectable segment currently
viewed by the debugger.
VQA Vector
QA
segment
Set selectable
segment to absolute
segment
Set the current selectable data segment to
the specified absolute segment number.
? Segment Display code
segment and
selectable data
segment information
Displays space identifier for current code
segment, displays segment ID for current
selectable data segment brought into use
by USESEGMENT or SEGMENT_USE_,
and displays segment ID for current
selectable data segment brought into use
by Debug VQ command.
Table 3-5. Privileged Commands (page 1 of 2)
Command Meaning Description
FREEZE Freeze Disables the processor and asserts a freeze on other
processors.
HALT Halt Halts the processor.