Are you on Linux? Do you want to get good backtraces from an asynchronous signal handler? Do not use abort(3). It generates terrible backtraces, use kill(getpid(), SIGABRT).
But only because abort() is a "noreturn" function and the compiler is smart about that, right? There shouldn't be anything "in Linux" that makes it worse than that, or is there? (Also: "raise(SIGABRT)" is shorter. :)
-
-
Yes, it's probably because both raise() and abort() are marked noreturn, and the compiler is smart about it.pic.twitter.com/UcoJKpwQcQ
-
Hmm.. now I'm confused. raise() should not be a noreturn function. E.g. raise(SIGWINCH) will almost certainly return. So it seems like something else is going on here. Strange.
- Show replies
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.