You're right. We would want __assert(), __assert_fail(), and __assert_perror_fail() to drop their messages into a known place, with a known format, in a process's core. Then we could extract it post-crash by looking for the right signature and recording the assertion message.
Obviously, a plain old SIGABRT won't give us anything useful. But rarely do those happen outside of assertions. -- provide abort() message access in core dumps https://launchpad.net/bugs/61938 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
