Code review comment for lp:~alan-griffiths/mir/demo_server-fatal-errors-core-dump
Revision history for this message
| Alan Griffiths (alan-griffiths) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
> 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:/
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?