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
Introduction
Debug Manual—421921-003
1-5
Entering a Breakpoint in a Process
DEBUG Procedure
The DEBUG procedure causes the current process to enter the debug state at the call
to Debug.
Example:
IF < THEN CALL DEBUG;
PROCESS_DEBUG_ Procedure
The PROCESS_DEBUG_ procedure can cause either the current process or the called
process to enter the debug state at the call.
Example of invoking Debug for the current process:
IF < THEN CALL PROCESS_DEBUG_ ; ! without parameters
Example of invoking Debug for another process identified by process handle:
ERROR := PROCESS_DEBUG_ ( PROCESSHANDLE, TERMINAL:LENGTH );
A now parameter in the PROCESS_DEBUG_ procedure immediately invokes the
debug state. To use the now parameter, the calling process must be executing under
the local super ID. The now parameter is required for debugging a system process,
including an input/output process (IOP). The same security considerations apply to the
use of PROCESS_DEBUG_ as to the use of the TACL DEBUG | DEBUGNOW
command.
DEBUGPROCESS Procedure
The DEBUGPROCESS procedure invokes debugging of the process specified by the
process-id parameter. The process-id can be in either a timestamp format or a
local or remote named format.
Example:
CALL DEBUGPROCESS (PROCESS-ID, ERROR );
A now parameter in the DEBUGPROCESS procedure immediately invokes the debug
state for the specified process. To use the now parameter, the calling process must be
executing under the local super ID (255, 255). The now parameter is required for
debugging a system process, including an input/output process (IOP).
Entering a Breakpoint in a Process
To have a process enter the debug state at a particular code location, set a code
breakpoint by using the B command when the process is in the debug state. Or, for a
memory location, set a memory-access breakpoint by using the BM command. After
Note. Using PROCESS_DEBUG_ to cause the current process to enter the debug state may
give unexpected results. To avoid any uncertainty, use DEBUG to cause the current process to
enter the debug state.