Files

Nick Fitzgerald 54aa720506 fuzzing: Refactor TableOps fuzz generator to allow GC with refs on the stack (#4016 )

This makes the generator more similar to `wasm-smith` where it is keeping track
of what is on the stack and making choices about what instructions are valid to
generate given the current stack state. This should in theory allow the
generator to emit GC calls while there are live refs on the stack.

Fixes #3917

2022-04-11 14:33:27 -07:00

src

fuzzing: Refactor TableOps fuzz generator to allow GC with refs on the stack (#4016 )

2022-04-11 14:33:27 -07:00

wasm-spec-interpreter

fuzz: improve wasm-spec-interpreter documentation, add library path (#4007 )

2022-04-11 09:07:58 -05:00

build.rs

Actually make spectest fuzzing deterministic

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

Cargo.toml

fuzzing: Refactor TableOps fuzz generator to allow GC with refs on the stack (#4016 )

2022-04-11 14:33:27 -07: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.