[wasmtime] Try fixing delivery of SIGILL/SIGSEGV to JIT #3335
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.
This is an attempt to apply the suggestions from #3316 to the fuzzing
infrastructure for the
wasmtime
target. This will hopefully allow thedelivery of SIGSEGV and SIGILL signals to the
wasmtime
program itself.These are expected signals when executing wasm code so we don't want the
fuzzer to treat all forms of the signal as a fatal error.
Unfortunately I'm not entirely sure how to test this locally, using the reproduction workflow this doesn't seem to have any effect, but it looks like this
*.options
file may not be picked up during thereproduce
workflow? I figure a shot in the dark could hopefully help here and I'm trusting @Dor1s as well :)