Mir server graphics driver crashes don't leave core files (no error report to Canonical)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Expired
|
Undecided
|
Unassigned |
Bug Description
Exceptions from mesa-kms graphics driver don't leave core files (not debuggable, errors never reported).
If my Mir server fails to start for some reason:
ERROR: /build/
Dynamic exception type: boost::
std::exception:
ERROR: /build/
Dynamic exception type: boost::
std::exception:
22, "Invalid argument"
then Canonical should get an error report by virtue of a core dump. But Mir does not leave a core for such errors.
The user's machine is left unusable and Canonical is never notified there is a problem that needs fixing.
Related branches
- Mir CI Bot: Approve (continuous-integration)
- Cemil Azizoglu (community): Approve
- Daniel van Vugt: Approve
- Alan Griffiths: Needs Information
-
Diff: 175 lines (+20/-13)10 files modifiedsrc/common/fatal/fatal.cpp (+1/-1)
src/include/platform/mir/options/configuration.h (+1/-1)
src/include/server/mir/default_server_configuration.h (+2/-2)
src/platform/options/default_configuration.cpp (+3/-3)
src/platform/symbols.map (+1/-1)
src/server/default_server_configuration.cpp (+2/-2)
tests/acceptance-tests/test_server_shutdown.cpp (+2/-3)
tests/unit-tests/graphics/mesa/kms/test_display.cpp (+2/-0)
tests/unit-tests/graphics/mesa/kms/test_real_kms_output.cpp (+4/-0)
tests/unit-tests/test_fatal.cpp (+2/-0)
description: | updated |
description: | updated |
summary: |
- Exceptions from mesa-kms graphics driver don't leave core files (not - debuggable, errors never reported) + Mir fatal errors don't leave core files (no error report to Canonical) |
summary: |
- Mir fatal errors don't leave core files (no error report to Canonical) + Mir server graphics driver crashes don't leave core files (no error + report to Canonical) |
Changed in mir: | |
milestone: | 0.24.0 → 0.25.0 |
The lack of a core is an option configured by the application using Mir (QtMir?)
You can override this by setting MIR_SERVER_ ON_FATAL_ ERROR_EXCEPT (or pass --on-fatal- error-abort on the command line).