Files

Peter Huene da539255a5 Use a much lower memory page limit for pooling allocator fuzzing. (#3795 )

This commit makes it such that the pooling allocator will be configured with a
much lower upper bound for memory pages, which will greatly reduce the
likelihood that the fuzzer memory limits will be hit from having too many
memories from too many instances committed.

2022-02-14 10:18:29 -06:00

src

Use a much lower memory page limit for pooling allocator fuzzing. (#3795 )

2022-02-14 10:18:29 -06: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

Fuzz using precompiled modules on CI (#3788 )

2022-02-10 11:55:18 -06: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.