SYNOPSIS<\/a>
DESCRIPTION<\/a>
RETURN VALUE<\/a>
ERRORS<\/a>
ATTRIBUTES<\/a>
CONFORMING TO<\/a>
NOTES<\/a>
SEE ALSO<\/a>
COLOPHON<\/a> <\/p>\n
\n
NAME <\/a> <\/h2>\nbsd_signal \u2212 signal handling with BSD semantics<\/p>\n
SYNOPSIS <\/a> <\/h2>\n#include <\/b><\/p>\ntypedef void (*sighandler_t)(int);<\/b><\/p>\n
sighandler_t bsd_signal(int<\/b> signum<\/i>, sighandler_t<\/b> handler<\/i>);<\/b><\/p>\n
Feature Test Macro Requirements for glibc (see feature_test_macros<\/b>(7)):<\/p>\n
bsd_signal<\/b>():<\/p>\n
Since glibc 2.26:
_XOPEN_SOURCE >= 500
&& ! (_POSIX_C_SOURCE\u00a0>=\u00a0200809L)
Glibc 2.25 and earlier:
_XOPEN_SOURCE<\/p>\n
DESCRIPTION <\/a> <\/h2>\nThe bsd_signal<\/b>() function takes the same arguments, and performs the same task, as signal<\/b>(2).<\/p>\n
The difference between the two is that bsd_signal<\/b>() is guaranteed to provide reliable signal semantics, that is: a) the disposition of the signal is not reset to the default when the handler is invoked; b) delivery of further instances of the signal is blocked while the signal handler is executing; and c) if the handler interrupts a blocking system call, then the system call is automatically restarted. A portable application cannot rely on signal<\/b>(2) to provide these guarantees.<\/p>\nRETURN VALUE <\/a> <\/h2>\nThe bsd_signal<\/b>() function returns the previous value of the signal handler, or SIG_ERR<\/b> on error.<\/p>\nERRORS <\/a> <\/h2>\nAs for signal<\/b>(2).<\/p>\nATTRIBUTES <\/a> <\/h2>\nFor an explanation of the terms used in this section, see attributes<\/b>(7).<\/p>\n
#include typedef void (*sighandler_t)(int);<\/b><\/p>\n sighandler_t bsd_signal(int<\/b> signum<\/i>, sighandler_t<\/b> handler<\/i>);<\/b><\/p>\n Feature Test Macro Requirements for glibc (see feature_test_macros<\/b>(7)):<\/p>\n bsd_signal<\/b>():<\/p>\n Since glibc 2.26: The bsd_signal<\/b>() function takes the same arguments, and performs the same task, as signal<\/b>(2).<\/p>\n The difference between the two is that bsd_signal<\/b>() is guaranteed to provide reliable signal semantics, that is: a) the disposition of the signal is not reset to the default when the handler is invoked; b) delivery of further instances of the signal is blocked while the signal handler is executing; and c) if the handler interrupts a blocking system call, then the system call is automatically restarted. A portable application cannot rely on signal<\/b>(2) to provide these guarantees.<\/p>\n The bsd_signal<\/b>() function returns the previous value of the signal handler, or SIG_ERR<\/b> on error.<\/p>\n As for signal<\/b>(2).<\/p>\n For an explanation of the terms used in this section, see attributes<\/b>(7).<\/p>\n
_XOPEN_SOURCE >= 500
&& ! (_POSIX_C_SOURCE\u00a0>=\u00a0200809L)
Glibc 2.25 and earlier:
_XOPEN_SOURCE<\/p>\nDESCRIPTION <\/a> <\/h2>\n
RETURN VALUE <\/a> <\/h2>\n
ERRORS <\/a> <\/h2>\n
ATTRIBUTES <\/a> <\/h2>\n
![\"Image](\"grohtml-1581011.png\")
<\/p>\n