[regression] Fatal DRM errors from a compositing thread have no usable stack trace
Bug #1316867 reported by
Daniel van Vugt
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Won't Fix
|
High
|
Unassigned | ||
| 0.4 |
Won't Fix
|
High
|
Unassigned | ||
| 0.5 |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
Fatal DRM errors from a compositing thread have no usable stack trace. This is a regression of bug 1237332 caused by this landing:
https:/
An example of the problem is seen in bug 1294510 where the available stack traces are completely useless.
Related branches
lp:~vanvugt/mir/fatal-error
- Cemil Azizoglu (community): Disapprove
- Robert Carr (community): Needs Fixing
- Alexandros Frantzis (community): Needs Fixing
- PS Jenkins bot (community): Approve (continuous-integration)
- Alan Griffiths: Needs Fixing
- Chris Halse Rogers: Approve
- Gerry Boland (community): Needs Information
- Michał Sawicz: Pending requested
-
Diff: 587 lines (+256/-79)13 files modifiedinclude/shared/mir/fatal.h (+52/-0)
src/platform/graphics/mesa/CMakeLists.txt (+2/-2)
src/platform/graphics/mesa/display_buffer.cpp (+9/-8)
src/platform/graphics/mesa/real_kms_output.cpp (+18/-29)
src/shared/CMakeLists.txt (+1/-0)
src/shared/fatal/CMakeLists.txt (+3/-0)
src/shared/fatal/fatal.cpp (+43/-0)
tests/acceptance-tests/CMakeLists.txt (+1/-0)
tests/acceptance-tests/test_server_shutdown.cpp (+34/-0)
tests/unit-tests/CMakeLists.txt (+2/-0)
tests/unit-tests/graphics/mesa/test_display.cpp (+27/-27)
tests/unit-tests/graphics/mesa/test_real_kms_output.cpp (+15/-13)
tests/unit-tests/test_fatal.cpp (+49/-0)
| summary: |
- [regression] Fatal exceptions raised in a compositing thread have no - usable stack trace + [regression] Fatal DRM errors from a compositing thread have no usable + stack trace |
| description: | updated |
| tags: | added: regression |
| Changed in mir: | |
| status: | Triaged → In Progress |
| description: | updated |
| Changed in mir: | |
| milestone: | 0.2.0 → 0.3.0 |
| Changed in mir: | |
| milestone: | 0.3.0 → 0.4.0 |
| Changed in mir: | |
| milestone: | 0.4.0 → 0.5.0 |
| tags: | added: rtm14 |
| Changed in mir: | |
| milestone: | 0.5.0 → 0.6.0 |
| tags: | removed: rtm14 |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #1 |
| Changed in mir: | |
| status: | In Progress → Triaged |
| milestone: | 0.6.0 → none |
| assignee: | Daniel van Vugt (vanvugt) → nobody |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #2 |
Revision history for this message
| Alan Griffiths (alan-griffiths) wrote | #3 |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #4 |
Revision history for this message
| Alan Griffiths (alan-griffiths) wrote | #5 |
| Changed in mir: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
The team has voted that exceptions are preferred over the ability to debug crash reports, so this bug is not getting fixed any time soon. Maybe we can find middle ground in future.