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-12
48
48
Cause. Debug could not access memory. See error message 13 for the list of
reasons.
Effect. The command is not executed.
Recovery. Check the address in the specified command to make sure that it is valid.
Make sure that the PIN still exists.
49
Cause. The FN command stops every time it reaches a byte address where the low-
order 17 bits are zero.
Effect. The command stops searching.
Recovery. To continue the search in the next unitary segment, enter the FN command
with the given 32-bit address.
50
Cause. The FN command stopped searching at the indicated address for the given
reason (see error message 13 for the list of reasons). This error normally occurs when
the end of the allocated memory is reached.
Effect. The executed command cannot go beyond the indicated address.
Recovery. Specify new values for the FN command or enter some other Debug
command that you want.
51
Cause. The FNL command stops every time it reaches a byte address where the low-
order 17 bits are zero.
Effect. The command stops searching.
Recovery. To continue the search in the next unitary segment, specify the FNL
command with the given 32-bit address.
Error accessing memory: reason.
FN reached address boundry. To continue, enter the following address:
address.
FN stopped searching at the following address: address, reason.
FNL reached address boundry. To continue, enter the following address:
address.