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.
** Also affects: platform-api (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mir
Importance: Medium => High
** Changed in: platform-api (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233988
Title:
With Mir enabled: maliit-server crashed with SIGABRT in
__gnu_cxx::__verbose_terminate_handler(), thrown from
mir::client::DisplayConfiguration::copy_to_client()
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1233988/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
