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 …
Right now it *is* catchable, just because we didn't have a good way to make it non-catchable. Now the tail of abort() provides a way to do so, if we want to.
-
-
I know, it just always felt like an accident that really violated intent.
-
Yeah I'd even considered SIGKILL before, but it's unfriendly to debugging.
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.