After thinking about this (and related mono failures which also have an
unusable backtrace with SIGABRT), I think it's best to just ignore
SIGABRT in apport for edgy until we find a good solution for grabbing
the abort() message (and likewise mono's stderr on SIGABRT).
** Changed in: glibc (Ubuntu)
Status: Needs Info => Confirmed
--
provide abort() message access in core dumps
https://launchpad.net/bugs/61938
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
