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-26
103
103
Cause. The command tried to set a code breakpoint at a location where a Memory
Access Breakpoint either exists in same process or in all processes in same processor.
Effect. The command is not executed.
Recovery. Try the command after removing the existing Memory Access Breakpoint
at the same location.
104
Cause. The command tried to set an all process Memory Access Breakpoint at a
location where a code breakpoint either exists in same process or in all processes in
same processor.
Effect. The command is not executed.
Recovery. Try the command after removing the existing code breakpoint at the same
location.
105
Cause. The command tried to set an all process code breakpoint at a location where a
Memory Access Breakpoint either exists in same process or in all processes in same
processor.
Effect. The command is not executed.
Recovery. Try the command after removing the existing Memory Access Breakpoint
at the same location.
Cannot set the code breakpoint at this address as Memory Access Breakpoint
already exists at given location.
Cannot set the Memory Access Breakpoint in all processes at this address as a
code breakpoint already exists at given location.
Cannot set the code breakpoint in all processes at this address as Memory
Access Breakpoint already exists at given location.