Files

Andrew Brown 7fa89c4a4f [fuzz] Fix order of operands passed in to wasm-spec-interpreter (#4672 )

In #4671, the meta-differential fuzz target was finding errors when
running certain Wasm modules (specifically `shr_s` in that case).
@conrad-watt diagnosed the issue as a missing reversal in the operands
passed to the spec interpreter. This change fixes #4671 and adds an
additional unit test to keep it fixed.

2022-08-10 09:55:33 -05:00

src

wasmtime: Add a Config::native_unwind_info method (#4643 )

2022-08-08 13:54:51 -07:00

wasm-spec-interpreter

[fuzz] Fix order of operands passed in to wasm-spec-interpreter (#4672 )

2022-08-10 09:55:33 -05:00

build.rs

Actually make spectest fuzzing deterministic

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

Cargo.toml

implement fuzzing for component types (#4537 )

2022-08-04 12:02:55 -05: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.