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-14
56
56
Cause. The VQ command attempted to restore the current segment indicated in the
PCB of the vectored PIN, but the attempt failed.
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.
57
Cause. The specified segment number in the VQ command was greater than the last
valid segment ID, or the specified segment ID is accessible only through privileged
mode.
Effect. The command is not executed.
Recovery. Make sure that the segment number you specified is not greater than the
segment ID. If the segment number is correctly specified, then make sure that you are
in privileged mode.
58
Cause. The VQ command could not access the segment number.
Effect. The command is not executed.
Recovery. Make sure that the specified segment number has been allocated by the
program.
59
Cause. The F command did not find a valid process file segment (PFS).
Effect. The command is not executed.
Recovery. The process might not have PFS allocated for the current PIN at this point
of process startup. This error can also indicate that Debug or some other part of the
operating system has a problem. If this problem persists, contact your service provider.
Cannot restore current segment in vectored PIN.
Segment number is invalid or requires PRV ON.
Cannot use segment.
Invalid PFS.