Hmm, I'm running into more xserver crash bugs with this issue. The
retracer posts a truncated (unhelpful) stacktrace (printing 2-3 levels
of stack then saying something about dwarf op codes), then deletes the
core file from the bug report. If I can get to a dupe bug before the
retracer hits it, I can get a useful backtrace out of it by running gdb
on it by hand. So it's not that the crash file was corrupted or
anything like theorized in comment #2, just that the retracer is broken.
Pitti, could you please disable the retracer from operating on the xorg-
server bug reports for now? There seem to be few enough crashers that I
can handle them by hand (actually, I'm finding using gdb on the core
file directly gives me more interesting info than the retracer gives
anyway). Thanks!
** Changed in: apport (Ubuntu Natty)
Status: Incomplete => Triaged
** Changed in: apport (Ubuntu Natty)
Milestone: None => natty-alpha-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/705572
Title:
retracer attaching incomplete backtrace
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
