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 …
I don't understand the "no, please keep it" aspect. Current behavior is crashing with a SIGSEGV or SIGILL (arch dependent) that could be caught just like any other one. Proposal is generating an uncatchable SIGABRT instead.
-
-
I meant option #2
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.