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-15
60
60
Cause. You did not indicate whether a memory-access breakpoint was a READ,
READ-WRITE, WRITE, or change (C) breakpoint.
Effect. The command is not executed.
Recovery. Specify one of the valid memory access types listed in the message text
and retry the command.
61
Cause. The memory manager indicated that the specified address is not a code
location.
Effect. The command is not executed.
Recovery. Make sure that specified address is in the code space (verify the address
with the AMAP command, if necessary).
62
Cause. Either command strings are not allowed or one had been specified previously.
Effect. The command is not executed.
Recovery. Do not use command strings when the change (C) access type is specified
with the BM command.
63
Cause. You specified a combination of options for the BM command that is not
allowed.
Effect. The command is not executed.
Recovery. Do not use conditions or trace breakpoint when the C access type is
specified with the BM command.
Invalid MAB access type. Expecting R, RW, W, or C.
Address is not in code location.
Command string is not allowed or was specified previously.
Condition or trace breakpoint is not allowed.