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

Panic support #34

Closed
carlpaten opened this issue Jan 20, 2016 · 2 comments
Closed

Panic support #34

carlpaten opened this issue Jan 20, 2016 · 2 comments
Assignees
Milestone

Comments

@carlpaten
Copy link

Rust implements "panics" (equivalent to C++ exceptions). They're used throughout the standard library, including when allocating memory through Box::new.

To support panics, we need to implement ::rt::begin_unwind and possibly ::rt::begin_unwind_fmt. A good first implementation would print to the emergency console and immediately crash.

Enables:

@carlpaten carlpaten added this to the M2 milestone Jan 20, 2016
This was referenced Jan 20, 2016
@carlpaten carlpaten modified the milestones: M3, M2 Feb 4, 2016
@carlpaten
Copy link
Author

I believe this worked before the Rust compiler switched from rust_begin_unwind to rust_fail. Fixing in M3.

@kanetkarster
Copy link
Contributor

Based off a recommendation from "Set Up Rust" we'll focus on adding this feature later. Currently, panicking will simply print an error message as CRust closes

@kanetkarster kanetkarster modified the milestones: Arbitrary future, M3 Feb 6, 2016
@carlpaten carlpaten assigned carlpaten and unassigned kanetkarster Feb 12, 2016
@carlpaten carlpaten modified the milestones: M3, Arbitrary future Feb 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants