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

Figure out how to handle failure outside of task context #5161

Closed
brson opened this issue Feb 28, 2013 · 6 comments
Closed

Figure out how to handle failure outside of task context #5161

brson opened this issue Feb 28, 2013 · 6 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@brson
Copy link
Contributor

brson commented Feb 28, 2013

Currently the runtime aborts. We can probably do better.

@ghost ghost assigned brson Apr 29, 2013
@catamorphism
Copy link
Contributor

Assigning to @brson -- de-milestone/de-assign if necessary.

@brson
Copy link
Contributor Author

brson commented May 1, 2013

Consider this related to #4419. I have some progress on this and generally know what I want to do. In the new scheduler I have a type called LocalServices that contains all the runtime capabilities required by the language itself. Tasks are one provider of LocalServices but there can be other.

This isn't a priority for me though. Demilestoning.

@metajack
Copy link
Contributor

revisitng for triage; nothing to add

@metajack
Copy link
Contributor

triage bump

1 similar comment
@flaper87
Copy link
Contributor

triage bump

@alexcrichton
Copy link
Member

This was changed recently in 0c7c93b to simply attempt to unwind. If there is no "catch frame" available, only then do we abort. I believe that this is about as good as we can get, so I'm going to close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Development

No branches or pull requests

5 participants