github
/
cranelift
mirror of https://github.com/bytecodealliance/wasmtime.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
13547 Commits
49 Branches
140 Tags
128 MiB
 
 
 
Branch: main
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'main'
${ noResults }
cranelift/crates/fuzzing
Nick Fitzgerald b2025ead23
Switch to new "user" stack maps and use `i32` for GC refs in Wasmtime (#9082) 		3 months ago
..
src Switch to new "user" stack maps and use `i32` for GC refs in Wasmtime (#9082) 3 months ago
wasm-spec-interpreter Add `rust-version.workspace = true` to all crates (#9112) 3 months ago
Cargo.toml Add `rust-version.workspace = true` to all crates (#9112) 3 months ago
README.md Create a new `wasmtime-fuzzing` crate 5 years ago
build.rs Enforce `uninlined_format_args` for the workspace (#9065) 3 months ago

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.