Some interesting/peculiar findings: * The core problem is that, for some reason, the exception object which we throw is not caught by catch(...) clauses! * Using a non-empty message in std::runtime_error or another exception type (e.g. std::exception), avoids the failures * If in mir::GLibMainLoop::enqueue() we replace the invocation of the 'action' function object (which contains a throw) with a direct throw, the exception is caught properly.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1478213 Title: mir tests fail on armhf in the landing-16 PPA To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1478213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
