errors indicates a retraced crash but isn't showing a stack trace
Bug #1267112 reported by
Jean-Baptiste Lallement
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Daisy |
Fix Released
|
High
|
Brian Murray |
Bug Description
Several crash of Ubiquity (really libautopilot-gtk) have been uploaded to errors.ubuntu.com [1]. The page on errors.u.c indicates a retraced crash but isn't showing a stack trace for it.
These crashes are uploaded automatically with whoopsie-upload-all when automated tests [2] find a crash file.
[1] https:/
[2] https:/
Related branches
lp:~brian-murray/daisy/fix-python-detection
- Evan (community): Approve
-
Diff: 12 lines (+1/-1)1 file modifieddaisy/submit.py (+1/-1)
Changed in errors: | |
importance: | Undecided → High |
status: | New → Confirmed |
affects: | errors → daisy |
Changed in daisy: | |
assignee: | nobody → Brian Murray (brian-murray) |
status: | Confirmed → Fix Committed |
To post a comment you must log in.
I've looked into this a bit and manually queried the error tracker in an attempt to find the stack trace. One thing of note and that needs fixing is that get_stacktrace_ for_bucket in errors/cassandra.py (https:/ /bazaar. launchpad. net/~daisy- pluckers/ errors/ trunk/view/ head:/errors/ cassandra. py#L168) only checks 10 crashes. I manually changed my version of cassandra.py to get 300 crashes but I was still unable to find a Stacktrace or ThreadStacktrace for this particular problem.
Additionally, I grep'ed the retracing logs for the two instances (4b5ea464- a941-11e3- b525-2c768aafd0 8c, d25d6b60- a943-11e3- ae27-2c768aafd0 8c) of the crash that jibel reported the other day and did not find them being retraced at all.