Files

Nick Fitzgerald edf7f9f2bb wasmtime: Add lots of logging for externrefs and table_ops fuzz target (#4583 )

I essentially add these same logs back in every time I'm debugging something
related to this fuzz target or `externref`s in general. Probably like 5 times
I've added roughly these logs. We should just make them available whenever we
need them via `RUST_LOG=wasmtime_runtime=trace`.

This also changes a couple `if let`s to `unwrap`s that are now infallible after

2022-08-02 15:06:44 -07:00

src

wasmtime: Add lots of logging for externrefs and table_ops fuzz target (#4583 )

2022-08-02 15:06:44 -07:00

wasm-spec-interpreter

Add *.wast support for invoking components (#4526 )

2022-07-27 21:02:16 +00:00

build.rs

Actually make spectest fuzzing deterministic

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

Cargo.toml

Add *.wast support for invoking components (#4526 )

2022-07-27 21:02:16 +00: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.