Is an uncatchable SIGABRT better than a[n unintentionally] catchable SIGSEGV/SIGILL (which varies by arch) when dangerous/corrupted process state is detected? https://www.openwall.com/lists/musl/2018/09/17/2 …
Hope it made sense. The sense I intended was that a_crash() being catchable in the past was not an intended property, just a consequence of it being hard to prevent.
-
-
Yep. The parenthetical comment resulted in a more considered choice.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.