Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ signal(3) — Ultrix WS 1.1

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

kill(1)

kill(2)

ptrace(2)

sigblock(2)

sigpause(2)

sigsetmask(2)

sigstack(2)

sigvec(2)

setjmp(3)

tty(4)

signal(3)

NAME

signal − simplified software signal facilities

SYNTAX

#include <signal.h>

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

DESCRIPTION

The signal subroutine is a simplified interface to the more general sigvec(2) facility.

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.  For further information, see tty(.). 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
SIGTRAP5*Trace trap
SIGIOT6*IOT instruction
SIGEMT7*EMT instruction
SIGFPE8*Floating point exception
SIGKILL9Kill (cannot be caught 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
SIGURG16•Urgent condition present on socket
SIGSTOP17+Stop (cannot be caught or ignored)
SIGTSTP18+Stop signal generated from keyboard
SIGCONT19•Continue after stop
SIGCHLD20•Child status has changed
SIGTTIN21+Background read attempted from control terminal
SIGTTOU22+Background write attempted to control terminal
SIGIO23•I/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 size change
SIGUSR130User defined signal
SIGUSR231User defined signal
SIGCLDSystem V name for SIGCHLD
SIGABRTX/OPEN name for SIGIOT

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 occurrences 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() on a slow device (such as a terminal; but not a file) and during a wait(.).

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

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

RETURN VALUE

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

DIAGNOSTICS

The signal subroutine will fail and no action will take place if one of the following occur:

[EINVAL] The 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). 

NOTES  (VAX-11)

The handler routine can be declared:

handler(sig, code, scp)

Here sig is the signal number, into which the hardware faults and traps are mapped as defined below.  Code is a parameter which is either a constant as given below or, for compatibility mode faults, the code provided by the hardware.  The scp is a pointer to the struct sigcontext used by the system to restore the process context from before the signal.  Compatibility mode faults are distinguished from the other SIGILL traps by having PSL_CM set in the psl. 

The following defines the mapping of hardware traps to signals and codes.  All of these symbols are defined in < signal.h >:

   Hardware conditionSignalCode
 Arithmetic traps:
   Integer overflowSIGFPEFPE_INTOVF_TRAP
   Integer division by zeroSIGFPEFPE_INTDIV_TRAP
   Floating overflow trapSIGFPEFPE_FLTOVF_TRAP
   Floating/decimal division by zeroSIGFPEFPE_FLTDIV_TRAP
   Floating underflow trapSIGFPEFPE_FLTUND_TRAP
   Decimal overflow trapSIGFPEFPE_DECOVF_TRAP
   Subscript-rangeSIGFPEFPE_SUBRNG_TRAP
   Floating overflow faultSIGFPEFPE_FLTOVF_FAULT
   Floating divide by zero faultSIGFPEFPE_FLTDIV_FAULT
   Floating underflow faultSIGFPEFPE_FLTUND_FAULT
Length access controlSIGSEGVfaulting virtual addr
Protection violationSIGBUSfaulting virtual addr
Reserved instructionSIGILLILL_PRIVIN_FAULT
Customer-reserved instr.SIGEMT
Reserved operandSIGILLILL_RESOP_FAULT
Reserved addressingSIGILLILL_RESAD_FAULT
Trace pendingSIGTRAP
Bpt instructionSIGTRAP
Compatibility-modeSIGILLhardware supplied code
ChmeSIGSEGV
ChmsSIGSEGV
ChmuSIGSEGV

ENVIRONMENT

When your program is compiled using the System V environment the handler function does NOT remain installed after the signal has been delivered. 

Also, when a signal which is to be caught occurs during a read(),  write(), or ioctl() to a slow device (like a terminal, but not a file); or during a  pause();  or wait() that does not return immediately,  the  signal  handler  function will be executed, and then the interrupted  system  call  may return  a -1 to the calling process with errno set to EINTR. 

SEE ALSO

kill(1), kill(2), ptrace(2), sigblock(2), sigpause(2), sigsetmask(2), sigstack(2), sigvec(2), setjmp(3), tty(4)

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026