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

Debug Commands
Debug Manual—421921-003
4-63
P[AUSE] Command
•
Open System Services supports additional signals that can be specified for
signal-name. For more information about OSS signals, OSS users can refer to
the signal(4) topic in the reference page, either online or in the Open System
Services System Calls Reference Manual.
•
A user-written procedure must meet certain requirements to function as a signal
handler. For more information on how to write a signal handler, refer to the
description of the SIGACTION_INIT_ procedure in the Guardian Procedure Calls
Reference Manual.
•
If you are running Debug as the super ID (255, 25), a signal handler that you install
with the MH command might or might not be capable of executing in privileged
mode depending on whether the signal handler it replaced was capable of
executing in privileged mode. The level of privilege will be unchanged. If you are
not running Debug as the super ID, you can install only a nonprivileged signal
handler.
•
You can use the IH command to verify that the new signal handler or handler
action is in effect after installing it with the MH command.
Examples
In this example, the MH command is used to specify a signal handler for the signal
SIGFPE and then, for verification, the IH command is used to display signal-handling
information for the same signal.
243,04,00019-MH SIGFPE, oxh00030000
243,04,00019-IH SIGFPE
Signal Priv/Non Handler Mask[0:31] Mask[32:63] Flags
SIGFPE N 0x00030000 0x00000000 0x098700A1 0x000816E4
P[AUSE] Command
The PAUSE (or P) command momentarily suspends process execution. This
command is particularly useful when you are simultaneously debugging several
processes at the same terminal. The form of the PAUSE command is:
pause-time
is an expression that specifies the length of time, in 0.01-second units, that the
process is to pause for.
Example
119,01,00012-P #1000 ! Pauses the process (01,012) for 10 seconds.
P[AUSE] pause-time