Open System Services Programmer's Guide

Table 68 Signals Processed by Threads (continued)
DescriptionDefault ActionTypeNumberName
No memory availableTerminate with saveabendSynchronous23SIGNOMEM
Write on a pipe, no one to
read it
Terminate processAsynchronus13SIGPIPE
QuitTerminate with saveabendAsynchronous3SIGQUIT
Message queued on
$RECEIVE (currently not used)
Discard signalSynchronous19SIGRECV
Invalid address referenceTerminate with saveabendSynchronous11SIGSEGV
Stack overflowTerminate with saveabendSynchronous25SIGSTK
StopTerminate processProcess-level20
1
SIGSTOP
Software termination signalTerminate processAsynchronous15SIGTERM
Process loop timer time-outTerminate processProcess-level26SIGTIMEOUT
Interactive stopTerminate processProcess-level21SIGTSTP
Background read attempted
from controlling terminal
Stop processProcess-level29SIGTTIN
Background write attempted
to controlling terminal
Stop processProcess-level30SIGTTOU
Uncooperative process.
Supported for servers running
H-series RVUs only.
Discard signalProcess-level10SIGUNCP
Urgent condition on I/O
channel
Discard signalAsynchronous5SIGURG
User-defined signal 1Terminate processAsynchronous16SIGUSR1
User-defined signal 2Terminate processAsynchronous17SIGUSR2
Terminal device window size
changed
Discard signalSynchronous12SIGWINCH
1
Signal cannot be caught or ignored.
Using Signals
• The following signal features are not supported:
Job Control Signals. The stop a process or continue a process actions implied by these
signals are also not supported.
◦
◦ The Real-time Signals Extension option.
• Use the sigaction() function, not the signal() function, to specify the action to be taken
when a given signal is received.
• These OSS system and library functions support thread-aware signal handling:
alarm()
sigaction()
signal
sigpending()
sigsuspend()
sigwait()
pause()
sleep()
386 Using the POSIX User Thread (PUT) Model Library