#glibc just skips the signal blocking, possibly causing double signal delivery when fork() interrupts raise().
Correct AS-safe raise() on Linux requires 3+ syscalls because kernel can't be bothered to treat tid==0/-1 as "self". http://git.musl-libc.org/cgit/musl/tree/src/signal/raise.c?id=7d3512126db7044525cf402255e0a85ac68dc2e9 …
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@RichFelker high syscall count is concern for performance or other reasons? -
@eigma The main practical impact is performance (correct raise taking 3x as long as the naive one) but it's also just ugly.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.