-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catch block for boost::exception appears after std::exception in execution_monitor::execute() #147
Comments
Give a snippet, define uninformative, and please read the contribution file on how to file a bug ticket. |
If you prefer to use Boost Trac why you haven't disabled Issues tab on GitHub?
At the moment the exception will be catch as
Well.. I swapped the boost::exception && std::exception and the only difference was in showing "Unknown exception" message. Sorry, thought it will use boost::diagnostic_information() instead of unknown-exception phrase. But isn't it right to catch more narrowed (non generic) exceptions first? |
What happens if you derive only from |
@k15tfu Would you please test the branch |
… next-internal * topic/GH-147-boost-exception-before-std-exception: Change log Catching boost::exception before std::exception
In next |
… develop * topic/GH-147-boost-exception-before-std-exception: Change log Catching boost::exception before std::exception
In develop, closing. |
Tested, thanks! |
So, if I throw myexception defined as
struct myexception : std::exception, virtual boost::exception
it prints uninformative messageThe text was updated successfully, but these errors were encountered: