Lack of a core file/backtrace appears to be Mir's fault:
examples/server_example.cpp: char const command_fmt[] = "/usr/share/apport/recoverable_problem --pid %d";
No application should be doing that. We have error reporting built into the OS, which is more reliable.
Lack of a core file/backtrace appears to be Mir's fault: server_ example. cpp: char const command_fmt[] = "/usr/share/ apport/ recoverable_ problem --pid %d";
examples/
No application should be doing that. We have error reporting built into the OS, which is more reliable.
Try this: error-abort
$ ulimit -c unlimited
$ mir_demo_server --on-fatal-
Do you get a core file?