Files

Chris Fallin 4e26c13bbe Add basic epoch-interruption config to fuzzing options. (#3844 )

Without async fuzzing, we won't be able to test the most interesting
aspects of epoch interruption, namely the
interrupt/update-deadline/resume flow. However, the "trap on epoch
change" behavior works even for synchronous stores, so we can fuzz with
this the same way we fuzz with the interrupt flag.

2022-02-23 12:40:52 -08:00

src

Add basic epoch-interruption config to fuzzing options. (#3844 )

2022-02-23 12:40:52 -08:00

wasm-spec-interpreter

Remove spec interpreter fuzz target temporarily (#3399 )

2021-09-30 13:09:19 -05:00

build.rs

Actually make spectest fuzzing deterministic

2021-03-29 09:12:16 -07:00

Cargo.toml

wasm-mutate fuzz targets (#3836 )

2022-02-23 12:14:11 -08:00

README.md

Create a new wasmtime-fuzzing crate

2019-11-21 14:51:07 -08:00

README.md

Fuzzing Infrastructure for Wasmtime

This crate provides test case generators and oracles for use with fuzzing.

These generators and oracles are generally independent of the fuzzing engine that might be using them and driving the whole fuzzing process (e.g. libFuzzer or AFL). As such, this crate does not contain any actual fuzz targets itself. Those are generally just a couple lines of glue code that plug raw input from (for example) libFuzzer into a generator, and then run one or more oracles on the generated test case.

If you're looking for the actual fuzz target definitions we currently have, they live in wasmtime/fuzz/fuzz_targets/* and are driven by cargo fuzz and libFuzzer.