Red Hat Bugzilla – Bug 159085
errno is 0 when sigwait returns an error
Last modified: 2007-11-30 17:11:06 EST
For some reason I do not understand from looking at the code, which must be
related in some weird way to how glibc handles function calls, system calls,
etc., when sigwait returns an error code the value of errno is not preserved,
i.e., the errno value is returned as an error code from sigwait but errno is 0
when it's examined. The value of errno should be preserved, as it is on
non-Linux operating systems.
errno after sigwait is unspecified.
As sigwait's description doesn't mandate anything about errno value, it is
unspecified. The only requirement is that if errno was non-zero before sigwait,
it will not be set to 0 by the call. If you see errno becoming 0 when it
previously was non-zero, then please provide a testcase.
But to my knowledge nothing in glibc violates that requirement, especially not
sigwait, which on most architectures will simply not touch errno at all, only
return the error value as it is supposed to do.