1SIGNAL(2) Linux Programmer's Manual SIGNAL(2)
2
6 signal - ANSI C signal handling
7
9 #include <signal.h>
10 typedef void (*sighandler_t)(int);
12 sighandler_t signal(int signum, sighandler_t handler);
14
16 WARNING:
17 the behavior of signal() varies across UNIX versions, and has also
18 varied historically across different versions of Linux. Avoid its use:
19 use sigaction(2) instead. See Portability below.
20 signal() sets the disposition of the signal signum to handler, which is
22 either SIG_IGN, SIG_DFL, or the address of a programmer-defined func‐
23 tion (a "signal handler").
24 If the signal signum is delivered to the process, then one of the fol‐
26 lowing happens:
27 * If the disposition is set to SIG_IGN, then the signal is ignored.
29 * If the disposition is set to SIG_DFL, then the default action asso‐
31 ciated with the signal (see signal(7)) occurs.
32 * If the disposition is set to a function, then first either the dis‐
34 position is reset to SIG_DFL, or the signal is blocked (see Porta‐
35 bility below), and then handler is called with argument signum. If
36 invocation of the handler caused the signal to be blocked, then the
37 signal is unblocked upon return from the handler.
38 The signals SIGKILL and SIGSTOP cannot be caught or ignored.
40
42 signal() returns the previous value of the signal handler, or SIG_ERR
43 on error. In the event of an error, errno is set to indicate the
44 cause.
45
47 EINVAL signum is invalid.
48
50 POSIX.1-2001, POSIX.1-2008, C89, C99.
51
53 The effects of signal() in a multithreaded process are unspecified.
54 According to POSIX, the behavior of a process is undefined after it ig‐
56 nores a SIGFPE, SIGILL, or SIGSEGV signal that was not generated by
57 kill(2) or raise(3). Integer division by zero has undefined result.
58 On some architectures it will generate a SIGFPE signal. (Also dividing
59 the most negative integer by -1 may generate SIGFPE.) Ignoring this
60 signal might lead to an endless loop.
61 See sigaction(2) for details on what happens when the disposition
63 SIGCHLD is set to SIG_IGN.
64 See signal-safety(7) for a list of the async-signal-safe functions that
66 can be safely called from inside a signal handler.
67 The use of sighandler_t is a GNU extension, exposed if _GNU_SOURCE is
69 defined; glibc also defines (the BSD-derived) sig_t if _BSD_SOURCE
70 (glibc 2.19 and earlier) or _DEFAULT_SOURCE (glibc 2.19 and later) is
71 defined. Without use of such a type, the declaration of signal() is
72 the somewhat harder to read:
73 void ( *signal(int signum, void (*handler)(int)) ) (int);
75 Portability
77 The only portable use of signal() is to set a signal's disposition to
78 SIG_DFL or SIG_IGN. The semantics when using signal() to establish a
79 signal handler vary across systems (and POSIX.1 explicitly permits this
80 variation); do not use it for this purpose.
81 POSIX.1 solved the portability mess by specifying sigaction(2), which
83 provides explicit control of the semantics when a signal handler is in‐
84 voked; use that interface instead of signal().
85 In the original UNIX systems, when a handler that was established using
87 signal() was invoked by the delivery of a signal, the disposition of
88 the signal would be reset to SIG_DFL, and the system did not block de‐
89 livery of further instances of the signal. This is equivalent to call‐
90 ing sigaction(2) with the following flags:
91 sa.sa_flags = SA_RESETHAND | SA_NODEFER;
93 System V also provides these semantics for signal(). This was bad be‐
95 cause the signal might be delivered again before the handler had a
96 chance to reestablish itself. Furthermore, rapid deliveries of the
97 same signal could result in recursive invocations of the handler.
98 BSD improved on this situation, but unfortunately also changed the se‐
100 mantics of the existing signal() interface while doing so. On BSD,
101 when a signal handler is invoked, the signal disposition is not reset,
102 and further instances of the signal are blocked from being delivered
103 while the handler is executing. Furthermore, certain blocking system
104 calls are automatically restarted if interrupted by a signal handler
105 (see signal(7)). The BSD semantics are equivalent to calling sigac‐
106 tion(2) with the following flags:
107 sa.sa_flags = SA_RESTART;
109 The situation on Linux is as follows:
111 * The kernel's signal() system call provides System V semantics.
113 * By default, in glibc 2 and later, the signal() wrapper function does
115 not invoke the kernel system call. Instead, it calls sigaction(2)
116 using flags that supply BSD semantics. This default behavior is pro‐
117 vided as long as a suitable feature test macro is defined:
118 _BSD_SOURCE on glibc 2.19 and earlier or _DEFAULT_SOURCE in glibc
119 2.19 and later. (By default, these macros are defined; see fea‐
120 ture_test_macros(7) for details.) If such a feature test macro is
121 not defined, then signal() provides System V semantics.
122
124 kill(1), alarm(2), kill(2), pause(2), sigaction(2), signalfd(2), sig‐
125 pending(2), sigprocmask(2), sigsuspend(2), bsd_signal(3), killpg(3),
126 raise(3), siginterrupt(3), sigqueue(3), sigsetops(3), sigvec(3),
127 sysv_signal(3), signal(7)
128
130 This page is part of release 5.10 of the Linux man-pages project. A
131 description of the project, information about reporting bugs, and the
132 latest version of this page, can be found at
133 https://www.kernel.org/doc/man-pages/.
134Linux 2017-09-15 SIGNAL(2)