@RichFelker http://austingroupbugs.net/view.php?id=1201 … You can't have a process atomically unmaks a signal *and* wait can you? Normally there is a loop-and-retry pattern, or the child's signal ends in process termination. Feels like Monday :-)
It might be possible, however, to emulate the intended behavior of sigsuspend using sigwaitinfo (consume the signal then manually call the signal handler with the consumed info).