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-12
Header Message Information
Header Message Information
These messages appear (as info) in the header to indicate why your process entered
Debug:
- (no further information in the header message)
One of the following occurred: a call to Debug, a call to an undefined external
procedure, a Debug command entered through the command interpreter, a RUND
command, or a memory-access breakpoint taken while executing system code. In
the latter case, a message precedes the prompt.
-BREAKPOINT-
The process encountered a code breakpoint.
-MEMORY ACCESS BREAKPOINT-
The process encountered a memory-access breakpoint.
-MEMORY ACCESS BREAKPOINT- (WHILE IN SYSTEM CODE)
The process encountered a memory-access breakpoint while in system code. The
Debug prompt occurs when execution exits system code.
-MEMORY ACCESS BREAKPOINT- (WHILE IN LIBRARY CODE)
The process encountered a memory-access breakpoint while in system library
code. The Debug prompt occurs when execution exits the system library code.
- RISC BREAKPOINT ($PC= 0x704205E0) -
The process encountered a RISC breakpoint.
- SIGNAL signal-name -
The process received a signal, identified by signal-name, and the signal action
in effect is SIG_DEBUG.
sys,cpu,pin
[cmd]
is the Debug prompt.
The value of sys is the node (system) number in decimal
(assigned during SYSGEN).
The value of cpu is the number, in decimal, of the processor
module where the process is executing.
The value of pin is the five-digit process identification number,
in decimal, of the process.
The value of cmd is a Debug command. If the Debug command
appears at the prompt, you can press RETURN to continue
executing the command.