This was partially fixed by
apport (1.8-0ubuntu1) karmic; urgency=low
* New upstream release:
- Do not generally ignore SIGABRT any more. Try to extract the assertion
message from the core dump, and add it as "AssertionMessage" field. Mark
reports as unreportable if they do not have an assertion message and
crashed
with SIGABRT. This implements UbuntuSpec:security-karmic-apport-abort.
- report.py, add_hooks_info(): Add optional package/srcpackage argument.
Hooks
can use that to change the affected package or call hooks from different
packages.
- KDE frontend implementation of ui_question_userpass(), for crash databases
which need to ask for credentials.
- hookutils.py: New funtion attach_wifi() to add wireless network related
information to reports.
- Fix the test suite on current kernels; test/crash previously often failed
with python segfaults, since it killed the test processes too early.
-- Martin Pitt <[email protected]> Wed, 26 Aug 2009 13:19:51
+0200
Programs which call abort() without an assert()ion message shouldn't get
a crash report, since they are pretty useless according to our
developers.
** Changed in: apport (Ubuntu)
Status: New => Fix Released
--
apport fails to detect certain X crashes because libc calls abort()
https://bugs.launchpad.net/bugs/376692
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
