Absolutely. Let debuggers worry about these sorts of things, don't try to catch SIGSEGV. The just-in-case convenience is attack surface.
-
-
-
Speaking off. glibc writes a stack trace on heap corruption, if I recall correctly? That seems scary.
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.