The handler is registered with sigaction(), not sigprocmask(). Even if the purpose of writing sigprocmask() here was to mention blocked signals, the statement currently concerns the "addition" of blocked signals; signals blocked through sigprocmask() would already be present in the thread context of blocked signals. Fixes: e7a5700 (getcontext.3, signal.7: tfix) Signed-off-by: Dev Jain <dev.jain@xxxxxxx> --- man/man7/signal.7 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man/man7/signal.7 b/man/man7/signal.7 index 17e75c86d..09d30c678 100644 --- a/man/man7/signal.7 +++ b/man/man7/signal.7 @@ -295,7 +295,7 @@ execution of the handler.) Any signals specified in .I act\->sa_mask when registering the handler with -.BR sigprocmask (2) +.BR sigaction (2) are added to the thread's signal mask. The signal being delivered is also added to the signal mask, unless -- 2.34.1
