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

Unwinding improvements #76

Open
jethrogb opened this issue Jan 25, 2019 · 1 comment
Open

Unwinding improvements #76

jethrogb opened this issue Jan 25, 2019 · 1 comment
Labels
enhancement Intel SGX std/rustc Requires changes in Rust std/rustc

Comments

@jethrogb
Copy link
Member

When panicking with unwinding, the stack gets unwound before the enclave returns to userspace. This is annoying because setting breakpoints isn't really possible yet so there is no way to inspect the stack at the panic location. Unwinding will only happen if there's a catchpoint on the stack. If there isn't, an abort will be triggered. We can inspect the stack after an abort. main/thread::spawn call catch_unwind internally in rt.rs and thread/mod.rs. We could add logic such that catch_unwind is elided in some cases depending on the enclave configuration (e.g. DEBUG global).

@jethrogb jethrogb added enhancement std/rustc Requires changes in Rust std/rustc labels Jan 25, 2019
@jethrogb
Copy link
Member Author

Related #34, #105

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Intel SGX std/rustc Requires changes in Rust std/rustc
Projects
None yet
Development

No branches or pull requests

2 participants