diff options
author | Michael Kerrisk <mtk.manpages@gmail.com> | 2020-11-12 21:40:41 +0100 |
---|---|---|
committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2020-11-12 21:48:33 +0100 |
commit | b5277108b41c50d8befeb4c5b8ce20fb4c11f555 (patch) | |
tree | 1de76ea84787fb313a7d4daf815797c4d983aa3e | |
parent | f527d6fe30a52caed641fcd5e663402a761ddbe6 (diff) | |
download | man-pages-b5277108b41c50d8befeb4c5b8ce20fb4c11f555.tar.gz |
signal.7: Minor tweaks to the test on execution of signal handlers
Reported-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r-- | man7/signal.7 | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/man7/signal.7 b/man7/signal.7 index 8fb0f0c4aa..3b30ffa790 100644 --- a/man7/signal.7 +++ b/man7/signal.7 @@ -180,6 +180,7 @@ as well as any additional signals specified in when .BR sigaction (2) was called. +These signals are thus blocked while the handler executes. .RE .IP 2. The kernel constructs a frame for the signal handler on the stack. @@ -212,7 +213,9 @@ or the handler executes a new program with .BR execve (2)), then the final step is not performed. In particular, in such scenarios it is the programmer's responsibility -to restore the state of the signal mask, if that is desired. +to restore the state of the signal mask, +if it is desired unblock the signals that were blocked on entry +to the signal handler. .\" .SS Synchronously accepting a signal Rather than asynchronously catching a signal via a signal handler, |