Error reporting of asio exceptions from AsioDMConnection could be better
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity System Compositor |
Triaged
|
Low
|
Unassigned | ||
unity-system-compositor (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
At least in this one case.
Josh Arenson and I were debugging a problem with a greeter / lightdm / unity-system-
But the exception looked like:
"""
ERROR: Throw location unknown (consider using BOOST_THROW_
Dynamic exception type: boost::
std::exception:
"""
It took us a surprising amount of effort to track down where this was actually failing (which was the usc::AsioDMConn
I don't have a suggested fix, just a request to make similar failure-hunts easier. Or at the least, this specific error case more obvious.
I'm not sure this is fixable short of simply not using 3rd party code that throws exceptions. If it's fatal like this one is, we can't catch it and recover. We also can't modify the exception text to be more meaningful.