|
NAMEsigvec —
software signal facilities
LIBRARYStandard C Library (libc, -lc)SYNOPSIS#include <signal.h>
struct sigvec { void (*sv_handler)(); int sv_mask; int sv_flags; }; int sigvec (int
sig, struct sigvec
*vec, struct sigvec
*ovec);
DESCRIPTIONThis interface is made obsolete by
sigaction(2).
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 from further occurrence, the current process context is saved, and a new one is built. A process may specify a handler to which a signal is delivered, or specify that a signal is to be blocked or ignored. A process may also specify that a default action is to be taken by the system when a signal occurs. Normally, signal handlers execute on the current stack of the process. This may be changed, on a per-handler basis, so that signals are taken on a special signal stack. All signals have the same priority. Signal routines execute with the signal that caused their invocation blocked, but other signals may yet 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 0). It may be changed with a sigblock(2) or sigsetmask(2) call, or 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 normally the process will resume execution in the context from 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' signal handler (or until a sigblock(2) or sigsetmask(2) call is made). This mask is formed by taking the current signal mask, adding the signal to be delivered, and or'ing in the signal mask associated with the handler to be invoked. The The following is a list of all signals with names as in the
include file
Once a signal handler is installed, it remains installed until
another If a signal is caught during the system calls listed below, the
call is normally restarted. The call can be forced to terminate prematurely
with an After a fork(2) or vfork(2) all signals, the signal mask, the signal stack, and the restart/interrupt flags are inherited by the child. The execve(2) system call reinstates the default action for all signals which were caught and resets all signals to be caught on the user stack. Ignored signals remain ignored; the signal mask remains the same; signals that interrupt system calls continue to do so. NOTESThe mask specified in vec is not allowed to blockSIGKILL or SIGSTOP . This is
done silently by the system.
The RETURN VALUESThesigvec () function returns the value 0 if
successful; otherwise the value -1 is returned and the global variable
errno is set to indicate the error.
EXAMPLESOn the VAX-11 The handler routine can be declared:void 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. The
code argument is either a constant as given below or,
for compatibility mode faults, the code provided by the hardware
(Compatibility mode faults are distinguished from the other
ERRORSThesigvec () function will fail and no new signal
handler will be installed if one of the following occurs:
SEE ALSOkill(1), kill(2), ptrace(2), sigaction(2), sigaltstack(2), sigblock(2), sigpause(2), sigprocmask(2), sigsetmask(2), sigsuspend(2), setjmp(3), siginterrupt(3), signal(3), sigsetops(3), tty(4)BUGSThis manual page is still confusing.
Visit the GSP FreeBSD Man Page Interface. |