assertion failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
samba (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: squid
Ubuntu 9.10
squid version 2.7.STABLE6-
Som when I start up Ubuntu, I have an outstanding failure, which I try to report, but then I get a dialog box titled "Problem in squid" that says, "The problem cannot be reported: The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes."
ProblemType: Bug
Architecture: i386
Date: Mon Nov 9 13:01:37 2009
DistroRelease: Ubuntu 9.10
Package: squid 2.7.STABLE6-
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: squid
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
(gnome-
(gnome-
(polkit-
(nautilus:2074): Eel-CRITICAL **: eel_preferences
(nautilus:2529): Eel-CRITICAL **: eel_preferences
affects: | squid (Ubuntu) → apport (Ubuntu) |
Changed in samba (Ubuntu): | |
status: | New → Triaged |
affects ubuntu/samba
importance wishlist
Launchpad Bug Tracker [2009-11-10 21:54 -0000]:
> "The problem cannot be reported: The program crashed on an assertion
> failure, but the message could not be retrieved. Apport does not
> support reporting these crashes."
This is deliberate, to avoid creating a massive amount of bug reports
which are useless for developers. glibc and glib's assertion messages
are now fixed to set __abort_msg (symbol in glibc) which apport reads.
Apparently samba uses its own assert macros and thus should be updated
to either use the standard C assert or set __abort_msg.
(See 05_store_ assert_ message. patch in glib2.0 source)