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 Manual—421921-003
A-1
A Error Messages
This appendix lists the error messages that can occur when you enter a Debug
command.
1
Cause. The code breakpoint table is full. The new breakpoint cannot be entered.
Effect. The command is not executed.
Recovery. Clear an existing breakpoint to provide space in the table, then try again.
2
Cause. The command, as entered, has invalid syntax, or the command is allowed only
in privileged mode and the debugging session is in nonprivileged mode.
Effect. The command is not executed.
Recovery. Correct the command, and try again. For a privileged mode command, if
you are the super ID (255,255), enter the PRV command and try again.
3
Cause. An error occurred on an input-output request. The value of error-number is
the decimal number of the file-system error that occurred.
Effect. None.
Recovery. See the file-system errors in the Guardian Procedure Errors and Messages
Manual for corrective action. For example, the error “?14” (file-system error 14) reports
that a specified device does not exist on the particular system.
4
Cause. A breakpoint is already set at the specified location, or a memory-access
breakpoint is already set. The new breakpoint cannot be entered.
Effect. None.
Recovery. Informational message only; no corrective action is needed.
The breakpoint table is full.
Trace routine encountered a syntax error.
?error-number
Breakpoint already exists.