© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
BTW, you won't get a crash report either. Because although it starts out as a serious-sounding C++ exception, libmirclient converts that into a SIGHUP for consumption by C clients. And SIGHUP's default action is to terminate without dumping core.
Normally SIGHUP is the right answer, because most such exceptions are just "the server disconnected us or died". So we do want the client to die (or catch the signal), and to not bother us with a core dump.
However bug 1506358 is a special unusual case where Mir has accidentally mapped a serious exception indicating a programming error into a non-serious SIGHUP. We need to learn to tell the difference between "normal" (server died and disconnected) and abnormal (server's still running but libmirclient is broken) exceptions...