Skip to content

Ability to catch a trap/panic #986

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.

Sign up for GitHub

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

Jump to bottom
Closed
Hywan opened this issue Nov 20, 2019 · 2 comments
Closed

Ability to catch a trap/panic #986

Hywan opened this issue Nov 20, 2019 · 2 comments
Labels
🎉 enhancement New feature! 📦 lib-deprecated About the deprecated crates

Comments

@Hywan
Copy link
Contributor

Hywan commented Nov 20, 2019

When a panic happens, it is caught and the trap API is run. It ends up panicking, and the end user seems to have no way to catch it.

That would be great to expose an API to register functions that can be executed when a trap is run, or better, an API to catch a trap/panic.

It will be super helpful to run untrusted Wasm modules from various users, or for language integrations (we can pipe the Wasmer panic/trap API to the targeted language panic API).
@Hywan Hywan added 🎉 enhancement New feature! 📦 lib-deprecated About the deprecated crates labels Nov 20, 2019
@Michael-F-Bryan Michael-F-Bryan mentioned this issue Dec 9, 2019
Closed
@lexfrl
Copy link

lexfrl commented Mar 30, 2020 •
edited
Loading

Is there any way to propagate panic which happened in the imported host function today?

@Hywan
Copy link
Contributor Author

Hywan commented Oct 1, 2020

All panics are now handled by the public API. This issue is no more relevant.

@Hywan Hywan closed this as completed Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🎉 enhancement New feature! 📦 lib-deprecated About the deprecated crates
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lexfrl @Hywan