Let exit(0) end Wasm execution but continue proving #56
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SpaceManiac
changed the title
Forpee
approved these changes
Jun 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Wasmi's execution model includes a trap representation that models classic
exitcodes, which host functions can return usingErr(wasmi::core::Trap::i32_exit(0)).This is a tweak to
fn execution_tracethat catches suchexit(0)calls and considers them to be successful program executions and continues proving that trace, rather than erroring out.It's possible that this misses some important post-function-call tracing or cleanup deeper in the stack; I don't know zkEngine well enough to say.