Skip to content
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

Make sure no exceptions propagate into the thread manager #781

hkaiser opened this issue Jun 2, 2013 · 0 comments


None yet
1 participant
Copy link

commented Jun 2, 2013

Currently, any unhandled exception which is not a hpx::exception propagates into the thread manager causing the application to fail. All actions should have a catch(...) added which could handle those exceptions and reports them to the user.

Also, directly executed action currently do not handle any exceptions but propagate those to the calling code. This is inconsistent with non-directly executed actions and should be aligned.

@ghost ghost assigned hkaiser Jun 2, 2013

@hkaiser hkaiser closed this in c8a20ac Jun 2, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.