signal.5 (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

signal(5) signal(5)

NAME

signal: signal.h - description of signals

SYNOPSIS

#include <signal.h>

DESCRIPTION

The <signal.h> header deﬁnes the following symbolic constants, each of which expands to a distinct

constant expression of the type:

void (*)(int)

whose value matches no declarable function.

SIG_DFL Request for default signal handling.

SIG_ERR Return value from signal() in case of error.

SIG_HOLD Request that signal be held.

SIG_IGN Request that signal be ignored.

The following data types are deﬁned through

typedef:

sig_atomic_t Integral type of an object that can be accessed as an atomic entity, even in the pres-

ence of asynchronous interrupts

sigset_t Integral or structure type of an object used to represent sets of signals.

pid_t As described in

This header also declares the constants that are used to refer to the signals that occur in the system. Sig-

nals deﬁned here begin with the letters

SIG. Each of the signals have distinct positive integral values.

The value 0 is reserved for use as the null signal (see kill (2)). Additional implementation-dependent sig-

nals may occur in the system.

HP-UX supports multiple signal interfaces (see sigaction (2), signal (2), and sigset (3C)) that allow a pro-

cess to specify the action taken upon receipt of a signal.

The following signals are supported on all implementations. The default actions A (Abort), C (Continue),

I (Ignore), S (Stop) and T (Abnormal Termination) are explained after the table.

Default

Signal Action Description

SIGABRT A Process abort signal.

Same as SIGIOT.

SIGALRM T Alarm clock.

SIGBUS A Access to undeﬁned portion of a memory object.

SIGCHLD I Child process terminated or stopped.

Same as SIGCLD.

SIGCLD I Same as SIGCHLD (also see WARNINGS below).

SIGCONT C Continue executing, if stopped.

SIGEMT A Software generated signal.

SIGFPE A Erroneous arithmetic operation.

SIGHUP THangup.

SIGILL A Illegal instruction.

SIGIO I Asynchronous I/O signal; see select(2).

Same as SIGPOLL.

SIGIOT A Process abort signal. Same as SIGABRT.

SIGINT T Terminal interrupt signal.

SIGKILL T Kill (cannot be caught or ignored).

SIGLOST A File lock lost (NFS ﬁle locking).

SIGPIPE T Write on a pipe with no one to read it.

SIGPOLL T Pollable event.

SIGQUIT A Terminal quit signal.

HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1

Summary of content (10 pages)

PAGE 1
signal(5) signal(5) NAME signal: signal.h - description of signals SYNOPSIS #include DESCRIPTION The header defines the following symbolic constants, each of which expands to a distinct constant expression of the type: void (*)(int) whose value matches no declarable function. SIG_DFL Request for default signal handling. SIG_ERR Return value from signal() in case of error. SIG_HOLD Request that signal be held. SIG_IGN Request that signal be ignored.
PAGE 2
signal(5) signal(5) SIGSEGV SIGSTOP SIGTERM SIGTSTP SIGTTIN SIGTTOU SIGUSR1 SIGUSR2 SIGPOLL SIGPROF SIGPWR SIGSYS SIGTRAP SIGURG SIGVTALRM SIGWINCH SIGXCPU SIGXFSZ SIGRTMIN SIGRTMAX A S T S S S T T T T I A A I T I A A T T Invalid memory reference. Stop executing (cannot be caught or ignored). Termination signal. Terminal stop signal. Background process attempting read. Background process attempting write. User-defined signal 1. User-defined signal 2. Pollable event. Profiling timer expired.
PAGE 3
signal(5) signal(5) sigset_t sa_mask set of signals to be blocked during execution of the signal handling function int sa_flags special flags void (*) (int, siginfo_t *, void *) sa_sigaction pointer to signal handler function or one of the macros SIG_IGN or SIG_DFL The storage occupied by sa_handler and sa_sigaction may overlap, and a portable program must not use both simultaneously. The following are declared as constants: SA_NOCLDSTOP Do not generate SIGCHLD when children stop.
PAGE 4
signal(5) signal(5) The signal specified in sigev_signo will be generated for the process when the event of interest occurs. If SA_SIGINFO is set for that signal number, then the signal will be queued to the process, and the value specified in sigev_value will be the sigev_value component of the generated signal. If SA_SIGINFO is not set for that signal number, it is unspecified whether the signal is queued, and what value, if any, is sent.
PAGE 5
signal(5) signal(5) ILL_PRVREG ILL_COPROC ILL_BADSTK privileged register coprocessor error internal stack error SIGFPE FPE_INTDIV FPE_INTOVF FPE_FLTDIV FPE_FLTOVF FPE_FLTUND FPE_FLTRES FPE_FLTINV FPE_FLTSUB integer divide by zero integer overflow floating point divide by zero floating point overflow floating point underflow floating point inexact result invalid floating point operation subscript out of range SIGSEGV SEGV_MAPERR SEGV_ACCERR address not mapped to object invalid permissions for mapped
PAGE 6
signal(5) void int (*bsd_signal(int sig, void (*func)(int)))(int); kill(pid_t pid, int sig); int int int int killpg(pid_t pgrp, int sig); raise(int sig); sigaction(int sig, const struct sigaction *act, struct sigaction *oact); sigaddset(sigset_t *set, int signo); int int int int sigaltstack(const stack_t *ss, stack_t *oss); sigdelset(sigset_t *set, int signo); sigemptyset(sigset_t *set); sigfillset(sigset_t *set); int int int int sighold(int sig); sigignore(int sig); siginterrupt(int sig, int flag);
PAGE 7
signal(5) signal(5) to refer to the thread’s context at the time of the interruption. Depending on the value of sig, code can be zero and/or scp can be NULL. The meanings of code and scp and the conditions determining when they are other than zero or NULL are implementation-dependent. It is possible for code to always be zero, and scp to always be NULL. The pointer scp, siginfop, and contextp are valid only during the context of the signal-catching function.
PAGE 8
signal(5) signal(5) Each PTHREAD_SCOPE_SYSTEM thread may define an alternate signal handling stack. Use of alternate signal stacks in PTHREAD_SCOPE_PROCESS threads will result in indeterminate behavior. Threadsafe Considerations Refer to thread_safety(5) for a list of libc and libpthread interfaces which are not thread-safe, cancellation points, cancel safe, async signal safe, and async cancel safe.
PAGE 9
signal(5) signal(5) STANDARDS CONFORMANCE : AES, SVID2, SVID3, XPG2, XPG3, XPG4, FIPS 151-2, POSIX.
PAGE 10
(Notes) A (Notes) sA 10 Hewlett-Packard Company −1− HP-UX 11i Version 3: September 2010