Files

Anton Kirilov 1481721c9d Enable back-edge CFI by default on macOS (#4720 )

Also, adjust the tests that are executed on that platform. Finally,
fix a bug with obtaining backtraces when back-edge CFI is enabled.

Copyright (c) 2022, Arm Limited.

2022-08-17 15:06:20 -05:00

src

Enable back-edge CFI by default on macOS (#4720 )

2022-08-17 15:06:20 -05: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

Upgrade wasm-tools crates, namely the component model (#4715 )

2022-08-17 16:17:34 +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.