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
Error Messages
Debug Manual—421921-003
A-3
13
13
Cause. An error occurred while attempting to display information pointed at by the
COMPADRS field of the breakpoint table. The reason is provided with the error
message, which can be one of the following:
Effect. Break information cannot be displayed.
Recovery. Try to fix the problem for the stated reason by clearing the breakpoint and
retrying the command. If retrying fails, contact your service provider with the
description of the problem.
14
Cause. The address was within the extended data segment or selectable segment,
but the address type was not being used in the process that is being debugged.
Effect. None.
Recovery. Check the program to make sure that it is using a data segment at this
point in the program. Also, check that you are debugging the correct program.
Internal error: Cannot access COMPADRS <reason>.
OK Occurs as an informational message only.
Bad PIN The specified PIN number is invalid.
Address not valid The specified address is invalid.
Unsupported The specified Debug version is not supported by the memory
manager.
KSEG1 address
given
Address specified in KSEG1 form is not valid.
REGSAVE required REGSAVE is required to qualify the address for the specified
address.
Out of bounds Read or write went beyond the limits of the allocated
memory.
Illegal Access Read or write access is illegal.
Cannot Access An unrecoverable error occurred while attempting to access
memory.
Address is in a relative data segment, but the program or the VQ command is
not using the segment.