Debug Manual

Introduction
Debug Manual—421921-003
1-8
How to Determine Process State on a Trap or Signal
If a TNS/R native or OSS process enters Debug because it has received a signal,
Debug automatically displays the name of the signal. Table 1-1 shows the TNS/R
native signals and how they correspond to trap conditions in a TNS process. Additional
signals are supported by Open System Services (OSS). For more information about
OSS signals, see the signal(4) topic in the reference page, either online or in the Open
System Services System Calls Reference Manual.
You can determine the TNS/R register settings (native mode) or the S, P, ENV, and L
register settings (TNS or accelerated mode) at the time of the trap by displaying the
register contents. Use the D command to display the contents of the TNS/R or TNS
environment registers and to display the space identifier. The meanings of the various
bits and the format of the Environment (ENV) register are illustrated in Figure 1-1 on
page 1-9.
For more information about TNS/R registers, see Section 2, Using Debug on TNS/R
Processors. For more information about space identifiers, see What Appears in the
4 Process loop-timer timeout
5 D-series limit does not fit into a C-series interface
8 (Under very unusual circumstances, a signal is delivered to a TNS
process and appears as a trap 8.)
11 Memory manager read error
12 No memory available
13 Uncorrectable memory error. Note that this error should not occur
because the millicode will halt the processor.
Table 1-1. Map of TNS/R Native Signals to Traps
Signal Name Description Trap Number
SIGABRT Abnormal termination (8)
SIGILL Invalid hardware instruction 1
SIGFPE Arithmetic overflow 2
SIGLIMIT Limits exceeded 5
SIGMEMERR Uncorrectable memory error 13
SIGMEMMGR Memory manager disk read
error
11
SIGNOMEM No memory available 12
SIGSEGV Invalid memory reference 0
SIGSTK Stack overflow 3
SIGTIMEOUT Process loop timeout 4
Trap Number Trap Condition (page 2 of 2)