sigwaitinfo.2: sigwaitinfo() can't be used to accept synchronous signals

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2017-03-15 08:24:10 +01:00
parent 55abe207b9
commit e3beca8848
1 changed files with 12 additions and 0 deletions

View File

@ -172,6 +172,18 @@ then exactly one of the threads will actually receive the
signal if it becomes pending for the process as a whole;
which of the threads receives the signal is indeterminate.
.BR sigwaitinfo ()
or
.BR sigtimedwait (),
can't be used to receive signals that
are synchronously generated, such as the
.BR SIGSEGV
signal that results from accessing an invalid memory address
or the
.BR SIGFPE
signal that results from an arithmetic error.
Such signals can be caught only via signal handler.
POSIX leaves the meaning of a NULL value for the
.I timeout
argument of