Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

WASM: Proper unwinding #6054

Closed
NikVolf opened this issue Jul 14, 2017 · 1 comment
Closed

WASM: Proper unwinding #6054

NikVolf opened this issue Jul 14, 2017 · 1 comment
Labels
F7-optimisation 💊 An enhancement to provide better overall performance in terms of time-to-completion for a task. M4-core ⛓ Core client code / Rust. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.

Comments

@NikVolf
Copy link
Contributor

NikVolf commented Jul 14, 2017 •
edited
Loading

For debugging purposes, runtime can handle much of the data passed to _rust_begin_unwind when contract code aborts on exception.
@NikVolf NikVolf added M4-core ⛓ Core client code / Rust. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. labels Jul 14, 2017
@5chdn 5chdn added the F7-optimisation 💊 An enhancement to provide better overall performance in terms of time-to-completion for a task. label Aug 7, 2017
@NikVolf
Copy link
Contributor Author

NikVolf commented Sep 6, 2017

After all, we added custom panic handlers

and the work is somewhat shown in #6474

@NikVolf NikVolf closed this as completed Sep 6, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
F7-optimisation 💊 An enhancement to provide better overall performance in terms of time-to-completion for a task. M4-core ⛓ Core client code / Rust. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@NikVolf @5chdn