SIGNAL(3) — C LIBRARY FUNCTIONS

NAME

signal − simplified software signal facilities

SYNOPSIS

#include <signal.h>

(∗signal(sig, func))()
void (∗func)();

DESCRIPTION

Signal is a simplified interface to the more general sigvec(2) facility. Programs that use signal in preference to sigvec are more likely to be portable to all UNIX systems.

A signal is generated by some abnormal event, initiated by a user at a terminal (quit, interrupt, stop), by a program error (bus error, etc.), by request of another program (kill), or when a process is stopped because it wishes to access its control terminal while in the background (see tty(4)). Signals are optionally generated when a process resumes after being stopped, when the status of child processes changes, or when input is ready at the control terminal. Most signals cause termination of the receiving process if no action is taken; some signals instead cause the process receiving them to be stopped, or are simply discarded if the process has not requested otherwise. Except for the SIGKILL and SIGSTOP signals, the signal call allows signals either to be ignored or to cause an interrupt to a specified location. The following is a list of all signals with names as in the include file <signal.h>:

SIGHUP1hangup
SIGINT2interrupt
SIGQUIT3∗quit
SIGILL4∗illegal instruction (other than A-line or F-line op code)
SIGTRAP5∗trace trap
SIGIOT6∗IOT instruction (not generated on Suns)
SIGEMT7∗EMT instruction (A-line or F-line op code)
SIGFPE8∗floating point exception
SIGKILL9kill (cannot be caught, blocked, or ignored)
SIGBUS10∗bus error
SIGSEGV11∗segmentation violation
SIGSYS12∗bad argument to system call
SIGPIPE13write on a pipe with no one to read it
SIGALRM14alarm clock
SIGTERM15software termination signal
SIGURG16urgent condition present on socket
SIGSTOP17†stop (cannot be caught, blocked, or ignored)
SIGTSTP18†stop signal generated from keyboard
SIGCONT19•continue after stop (cannot be blocked)
SIGCHLD20•child status has changed
SIGTTIN21†background read attempted from control terminal
SIGTTOU22†background write attempted to control terminal
SIGIO23i/o is possible on a descriptor (see
fcntl(2))
SIGXCPU24cpu time limit exceeded (see
setrlimit(2))
SIGXFSZ25file size limit exceeded (see
setrlimit(2))
SIGVTALRM26virtual time alarm (see
setitimer(2))
SIGPROF27profiling timer alarm (see
setitimer(2))
SIGWINCH28•window changed (see
win(4S))

The starred signals in the list above cause a core image if not caught or ignored.

If func is SIG_DFL, the default action for signal sig is reinstated; this default is termination (with a core image for starred signals) except for signals marked with • or †. Signals marked with • are discarded if the action is SIG_DFL; signals marked with † cause the process to stop. If func is SIG_IGN the signal is subsequently ignored and pending instances of the signal are discarded. Otherwise, when the signal occurs further occurences of the signal are automatically blocked and func is called.

A return from the function unblocks the handled signal and continues the process at the point it was interrupted. Unlike previous signal facilities, the handler func remains installed after a signal has been delivered.

If a caught signal occurs during certain system calls, causing the call to terminate prematurely, the call is automatically restarted. In particular this can occur during a read or write(2) on a slow device (such as a terminal; but not a file) and during a wait(2).

The value of signal is the previous (or initial) value of func for the particular signal.

After a fork(2) or vfork(2) the child inherits all signals. An execve(2) resets all caught signals to the default action; ignored signals remain ignored.

NOTES

The handler routine can be declared:

    handler(sig, code, scp)
    int sig, code;
    struct sigcontext ∗scp;

Here sig is the signal number. Code is a parameter of certain signals that provides additional detail. Scp is a pointer to the sigcontext structure (defined in <signal.h>), used to restore the context from before the signal.

CODES

The following defines the codes for signals which produce them. All of these symbols are defined in <signal.h>:

Hardware conditionSignalCode
Illegal instructionSIGILLILL_INSTR_FAULT
Privilege violationSIGILLILL_PRIVVIO_FAULT
Coprocessor protocol errorSIGILLILL_INSTR_FAULT
Trap #n (1 <= n <= 14)SIGILLILL_TRAPn_FAULT
^ ^ n’s above should be italicized ^
A-line op codeSIGEMTEMT_EMU1010
F-line op codeSIGEMTEMT_EMU1111
Integer division by zeroSIGFPEFPE_INTDIV_TRAP
CHK or CHK2 instructionSIGFPEFPE_CHKINST_TRAP
TRAPV or TRAPcc or cpTRAPccSIGFPEFPE_TRAPV_TRAP
IEEE floating point compare unorderedSIGFPEFPE_FLTBSUN_TRAP
IEEE floating point inexactSIGFPEFPE_FLTINEX_TRAP
IEEE floating point division by zeroSIGFPEFPE_FLTDIV_TRAP
IEEE floating point underflowSIGFPEFPE_FLTUND_TRAP
IEEE floating point operand errorSIGFPEFPE_FLTOPERR_TRAP
IEEE floating point overflowSIGFPEFPE_FLTOVF_FAULT
IEEE floating point signaling NaNSIGFPEFPE_FLTNAN_TRAP

RETURN VALUE

The previous action is returned on a successful call. Otherwise, −1 is returned and errno is set to indicate the error.

ERRORS

Signal will fail and no action will take place if one of the following occur:

[EINVAL] Sig is not a valid signal number.

[EINVAL] An attempt is made to ignore or supply a handler for SIGKILL or SIGSTOP.

[EINVAL] An attempt is made to ignore SIGCONT (by default SIGCONT is ignored).

Museum

Related Articles