oss-fuzz

Commit Graph

Author	SHA1	Message	Date
Alex Crichton	0dc597e53e	Add `handle_segv =1` to Wasmtime's options (#4266 ) * Add `handle_segv =1` to Wasmtime's options This is an attempt to handle #4264	2020-08-06 17:02:42 -07:00
Alex Crichton	ec58a65f33	[wasmtime] Fix default asan options (#3350 ) This fixes typo mistakes from #3335 where we actually want the opposite of the current defaults, not the current set of defaults!	2020-02-06 10:26:09 -08:00
Alex Crichton	94d0c3a7b4	[wasmtime] Try fixing delivery of SIGILL/SIGSEGV to JIT (#3335 ) This is an attempt to apply the suggestions from #3316 to the fuzzing infrastructure for the `wasmtime` target. This will hopefully allow the delivery 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.	2020-02-05 09:46:23 -08:00

Author

SHA1

Message

Date

Alex Crichton

0dc597e53e

Add `handle_segv =1` to Wasmtime's options (#4266 )

* Add `handle_segv =1` to Wasmtime's options

This is an attempt to handle #4264

2020-08-06 17:02:42 -07:00

Alex Crichton

ec58a65f33

[wasmtime] Fix default asan options (#3350 )

This fixes typo mistakes from #3335 where we actually want the opposite
of the current defaults, not the current set of defaults!

2020-02-06 10:26:09 -08:00

Alex Crichton

94d0c3a7b4

[wasmtime] Try fixing delivery of SIGILL/SIGSEGV to JIT (#3335 )

This is an attempt to apply the suggestions from #3316 to the fuzzing
infrastructure for the `wasmtime` target. This will hopefully allow the
delivery 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.

2020-02-05 09:46:23 -08:00

3 Commits