Code review comment for lp:~alan-griffiths/mir/demo_server-fatal-errors-core-dump

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

> Don't mind this; having Mir trigger apport on exceptions that reach
> server::run()¹ would be a way of getting crash reports without taking down the
> host process.
> ¹: https://wiki.ubuntu.com/Apport/DeveloperHowTo

Two questions:

1. That link seems to be a lot of information about customizing apport, but gives little about the options for triggering it. It seems we need to write a small python script and execute that. I assume that can be coded to grab a stack trace?

2. Is server::run() the right place? Threads have been joined and the stack has unwound by then. Surely we should be capturing information in the fatal_error() handler?

« Back to merge proposal