Files

Alex Crichton 44351cc4af fuzz: Increase more limits when spectest fuzzing (#3926 )

When using the pooling instance allocator for running spec tests we have
to make sure that the configured limits of the allocator aren't so low
as to cause the spec tests to fail due to resource exhaustion issues or
similar. This commit adds in minimum thresholds for instance size as
well as instance count. While here this goes ahead and refactors
everything here to look similar.

2022-03-14 11:35:17 -05:00

src

fuzz: Increase more limits when spectest fuzzing (#3926 )

2022-03-14 11:35:17 -05:00

wasm-spec-interpreter

Fix allowing an override of LIBGMP_PATHS (#3870 )

2022-03-02 11:41:59 -06:00

build.rs

Actually make spectest fuzzing deterministic

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

Cargo.toml

Move spec interpreter fuzzing behind a Cargo feature (#3871 )

2022-03-02 14:29:25 -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.