Signal(SIGINT, sig_int)

最新推荐文章于 2024-07-23 16:01:02 发布

lav1314

最新推荐文章于 2024-07-23 16:01:02 发布

阅读量1.7k

点赞数

文章标签： signal function portability system library include

本文链接：https://blog.csdn.net/lav1314/article/details/5034112

版权

#include <signal.h>

typedef void (*sighandler_t)(int);

sighandler_t signal(int signum, sighandler_t handler);


DESCRIPTION
The signal() system call installs a new signal handler for the signal
with number signum. The signal handler is set to sighandler which may
be a user specified function, or either SIG_IGN or SIG_DFL.

Upon arrival of a signal with number signum the following happens. If
the corresponding handler is set to SIG_IGN, then the signal is
ignored. If the handler is set to SIG_DFL, then the default action
associated to the signal (see signal(7)) occurs. Finally, if the han-
dler is set to a function sighandler then first either the handler is
reset to SIG_DFL or an implementation-dependent blocking of the signal
is performed and next sighandler is called with argument signum.

Using a signal handler function for a signal is called "catching the
signal". The signals SIGKILL and SIGSTOP cannot be caught or ignored.


RETURN VALUE
The signal() function returns the previous value of the signal handler,
or SIG_ERR on error.


PORTABILITY
The original Unix signal() would reset the handler to SIG_DFL, and Sys-
tem V (and the Linux kernel and libc4,5) does the same. On the other
hand, BSD does not reset the handler, but blocks new instances of this
signal from occurring during a call of the handler. The glibc2 library
follows the BSD behaviour.

If one on a libc5 system includes <bsd/signal.h> instead of <signal.h>
then signal is redefined as __bsd_signal and signal has the BSD seman-
tics. This is not recommended.

If one on a glibc2 system defines a feature test macro such as
_XOPEN_SOURCE or uses a separate sysv_signal function, one obtains
classical behaviour. This is not recommended.

Trying to change the semantics of this call using defines and includes
is not a good idea. It is better to avoid signal altogether, and use
sigaction(2) instead.


NOTES
According to POSIX, the behaviour of a process is undefined after it
ignores a SIGFPE, SIGILL, or SIGSEGV signal that was not generated by