NAME

sigvec − software signal facilities

USAGE

#include <signal.h> struct sigvec { int(*sv_handler)(); intsv_mask;  int sv_onstack; };
 
sigvec(sig, vec, ovec) int sig; struct sigvec *vec, *ovec;

DESCRIPTION

The system defines a set of signals that may be delivered to a process.  Signal delivery resembles the occurrence of a hardware interrupt: the signal is blocked, the current process context is saved, and a new one is built.  A signal may be blocked, ignored, or delivered to a handler, as the process requires.  A process may also specify a default action for the system to take when a given signal occurs.  Normally, signal handlers execute on the current stack of the process. 

All signals have the same priority.  While a signal routine executes, the signal that triggered it is blocked, although other signals may occur.  A global signal mask defines the set of signals currently blocked from delivery to a process.  The signal mask for a process is initialized from that of its parent (normally zero).  It may be changed with a sigblock(2) or sigsetmask(2) call, and when a signal is delivered to the process. 

When a signal condition arises for a process, the signal is added to a set of signals pending for the process.  If the signal is not currently blocked by the process, then it is delivered to the process.  When a signal is delivered, the current state of the process is saved, a new signal mask is calculated (as described below), and the signal handler is invoked.  The call to the handler is arranged so that, if the signal handling routine returns, the process will normally resume execution in the state it was in before the signal’s delivery.  If the process wishes to resume in a different context, then it must arrange to restore the previous context itself. 

When a signal is delivered to a process, a new signal mask is installed for the duration of the process’s signal handler (or until a sigblock or sigsetmask call is made).  This mask is formed by taking the current signal mask, adding the signal to be delivered, and including, with a logical OR, the signal mask associated with the handler to be invoked. 

Sigvec assigns a handler for a specific signal.  If vec is non-zero, it specifies a handler routine and mask to be used when delivering the specified signal.  Further, if sv_onstack is 1, some systems will deliver the signal to the process on a signal stack, as specified with sigstack(2).  (This feature is not implemented in DOMAIN/IX.)  If ovec is non-zero, the previous handling information for the signal is returned to the user. 

The following is a list of all signals with names as in the include file <signal.h>:

SIGHUP1hang-up
SIGINT2interrupt
SIGQUIT3quit
SIGILL4illegal instruction
SIGTRAP5trace trap
SIGIOT6IOT instruction
SIGEMT7EMT instruction
SIGFPE8floating-point exception
SIGKILL9kill (cannot be caught, blocked, or ignored)
SIGBUS10bus error
SIGSEGV11segmentation violation
SIGSYS12bad argument to system call
SIGPIPE13write on a pipe with no one to read it
SIGALRM14alarm clock
SIGTERM15software termination signal
SIGUSR116user-defined signal 1
SIGUSR217user-defined signal 2
SIGCLD18death of a child
SIGAPOLLO19DOMAIN System fault with no UNIX System equivalent
SIGSTOP20†stop, cannot be caught, held, or ignored
SIGTSTP21†stop signal generated from keyboard
SIGCONT22•continue after stop
SIGCHLD23•child status has changed
SIGTTIN24†background read attempted from control terminal
SIGTTOU25†background write attempted to control terminal
SIGIO  26I/O is possible on a descriptor
SIGTINT26input record is available at control terminal
SIGXCPU27cpu time limit exceeded
SIGXFSZ28file size limit exceeded
SIGVTALRM29virtual time alarm
SIGPROF30profiling timer alarm
SIGURG31•urgent condition present on socket

Once a signal handler is installed, it remains installed until another sigvec call is made, or an execve(2) is performed.  The default action for a signal may be reinstated by setting sv_handler to SIG_DFL; this default is termination except for signals marked with a bullet (•) or a dagger (†).  Signals marked with a bullet are discarded if the action is SIG_DFL; signals marked with a dagger cause the process to stop.  If sv_handler is SIG_IGN, the signal is subsequently ignored, and pending instances of the signal are discarded. 

If a caught signal occurs during certain system calls and causes the call to terminate prematurely, the call is automatically restarted.  This is especially likely to occur during a read(2) or write(2) on a slow device (e.g., a terminal) and during a wait(2). 

After a fork(2) or vfork(2), the child inherits all signals, the signal mask, and the signal stack. 

Execve(2) resets all caught signals to default action; ignored signals remain ignored; the signal mask remains the same; and the signal stack state is reset. 

NOTES

The signal stack feature is not implemented on DOMAIN Systems.  Calls to sigstack(2) always return 0.  Stack context is not changed. 

DOMAIN systems send the signal SIGAPOLLO whenever a fault occurs that is not otherwise mapped into a signal.  Typical generators of SIGAPOLLO include network failures, display-acquire timeouts, and disk full errors. 

The system does not allow the mask specified in vec to block SIGKILL, SIGSTOP, or SIGCONT. 

The handler routine can be declared as follows: handler(sig, code, scp) int sig, code; struct sigcontext *scp;

Here, sig is the signal number into which the hardware faults and traps are mapped as defined below.  Code is a 32-bit value.  If the signal is SIGAPOLLO, code is the DOMAIN System status code describing the fault.  (To generate a list of DOMAIN System status codes and brief explanations of their meanings, run the command /systest/ssr_util/all_stcode.)  Otherwise, code is a value associated with one of the constants listed below.  Scp is a pointer to the sigcontext structure (defined in <signal.h>), which is used to restore the context from before the signal. 

DOMAIN System Hardware traps are mapped to signals and codes as indicated below.  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 controlSIGSEGV
Protection violationSIGBUS
Reserved instructionSIGILLILL_RESAD_FAULT
Customer-reserved instr.SIGEMT
Reserved operandSIGILLILL_PRIVIN_FAULT
Reserved addressingSIGILLILL_RESOP_FAULT
Trace pendingSIGTRAP
Bpt instructionSIGTRAP

RETURN VALUE

A successful call returns zero.  A failed call returns -1 and sets errno as indicated below. 

ERRORS

Sigvec will fail and no new signal handler will be installed if one of the following occurs:

[EFAULT] Either vec or ovec points to memory that is not a valid part of the process’s address space. 

[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). 

RELATED INFORMATION

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