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-13
52
52
Cause. The FNL command stopped searching at the indicated address for the given
reason (see error message 13 for the list of reasons). This normally occurs when the
end of the allocated memory for the program is reached.
Effect. The executed command cannot go beyond the indicated address.
Recovery. Specify new values for the FNL command or enter some other Debug
command that you want.
53
Cause. The specified absolute-segment number for the VQA command was larger
than the number of absolute segments.
Effect. The command is not executed.
Recovery. Make sure that the specified absolute-segment number is within the range
of the VQA command.
54
Cause. The specified absolute-segment number for the VQA command cannot be
used.
Effect. The command is not executed.
Recovery. Contact your service provider with the description of the problem.
55
Cause. The VQ command cannot restore the original segment that was being used by
the program.
Effect. The command might or might not be executed.
Recovery. Check the current user segment syntax with the ? command. If you had not
specified the correct value, specify a correct value for the user segment and try again.
If the user segment value you specified is correct, contact your service provider with
the description of the problem.
FNL stopped searching at the following address: address, reason.
Absolute-segment number is too large.
Cannot use absolute-segment number.
Cannot restore user segment.