** Changed in: apport (Ubuntu)
Status: Triaged = Fix Committed
--
stacktrace comparisons
https://bugs.launchpad.net/bugs/269133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package apport - 0.142
---
apport (0.142) jaunty; urgency=low
* apport/report.py: Do not include lsb_release's stderr in the
DistroRelease: output.
* apport/hookutils.py: Fix attach_printing():
- Correct spelling or error_log.
- Do not call
261773 crashes in paintOutputRegion(), while 211107 crashes in
animWalkNext() (although the next stack frame is paintOutputRegion()). I
don't think we should generally auto-duplicate those 'fuzzy' matches,
since it easily leads to false positives.
** Changed in: apport (Ubuntu)
Status: New
Oh, in fact the second trace is also in animWalkNext(), however, the
stack trace is missing an address for it:
#0 animWalkNext (w=0x8710850) at animation.c:3252
it should be
#0 0xb58694e8 in animWalkNext (w=0x81eda10) at animation.c:3048
Smells like a gdb buglet. I don't know how common
** Changed in: apport (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
stacktrace comparisons
https://bugs.launchpad.net/bugs/269133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
