There is a second more likely explanation for the exception at /usr/include/c++/4.8/mutex:506.
That would be an invalid "this" pointer for DisplayConfiguration. Looking at mir_connection.cpp, it could happen if either:
(1) The client (platform-api) sets an invalid DisplayConfiguration on the MirConnection; or
(2) platform-api passes libmirclient an invalid MirConnection.
I'm not sure if there is any code path in which the fault could be in libmirclient. Looks most likely platform-api misusing the client API.
There is a second more likely explanation for the exception at /usr/include/ c++/4.8/ mutex:506. ation. Looking at mir_connection.cpp, it could happen if either: ation on the MirConnection; or
That would be an invalid "this" pointer for DisplayConfigur
(1) The client (platform-api) sets an invalid DisplayConfigur
(2) platform-api passes libmirclient an invalid MirConnection.
I'm not sure if there is any code path in which the fault could be in libmirclient. Looks most likely platform-api misusing the client API.