Mir

Mir server graphics driver crashes don't leave core files (no error report to Canonical)

Bug #1577106 reported by Daniel van Vugt
12
This bug affects 2 people
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/mir-pkdHET/mir-0.21.0+16.04.20160330/src/server/graphics/default_configuration.cpp(133): Throw in function mir::DefaultServerConfiguration::the_graphics_platform()::<lambda()>
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
std::exception::what: Exception while creating graphics platform
ERROR: /build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/platforms/mesa/server/common/display_helpers.cpp(256): Throw in function int mir::graphics::mesa::helpers::DRMHelper::open_drm_device(const std::shared_ptr<mir::udev::Context>&)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
std::exception::what: Error opening DRM device
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

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)
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

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).

Changed in mir:
assignee: nobody → Alan Griffiths (alan-griffiths)
milestone: none → 0.24.0
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Environment variables and command line options won't do. We need reliable and automatic always-on crash reports.

Revision history for this message
Mir CI Bot (mir-ci-bot) wrote :

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.24.0

Changed in mir:
status: New → Fix Committed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in mir:
status: Fix Committed → Triaged
Kevin DuBois (kdub)
Changed in mir:
milestone: 0.24.0 → 0.25.0
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Dropped severity. I'm not sure how many of these are left but we haven't hit any for a while.

Changed in mir:
assignee: Alan Griffiths (alan-griffiths) → nobody
importance: Critical → High
milestone: 0.25.0 → none
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

This no longer seems to be an issue

Changed in mir:
importance: High → Undecided
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Mir because there has been no activity for 60 days.]

Changed in mir:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.