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

> We don't really *want* to be capturing a core, surely; we know where the
> exception is thrown from, and the exception *should* have more useful
> information than a core. The call stack is generally uninteresting for these
> things.
>
> We'd just need to write a little Python script and pump roughly the output of
> boost_describe_exception into it...

Maybe we could use /usr/share/apport/recoverable_problem?