cargo-fuzz
cargo-fuzz copied to clipboard
rust-fuzz
Command line helpers for fuzzing
Apparently `cargo-fuzz` supports being used without sanitizers. This is mentioned on [Reddit](https://www.reddit.com/r/rust/comments/hg6x3s/cargofuzz_is_now_10x_faster_better_supports/) and in #158. After stumbling across this information I tried looking at the readme which claims: > Note:...
Now that libfuzzer has been [officially deprecated](https://llvm.org/docs/LibFuzzer.html#status) I was wondering if the maintainers of cargo-fuzz are interested to add [LibAFL](https://github.com/AFLplusplus/LibAFL) support to this crate directly. LibAFL is not only maintained,...
EDIT: See subsequent comments. Original title: "Publish release with `cfg(fuzzing_repro)`" * * * This feature is already [documented in the guide](https://rust-fuzz.github.io/book/cargo-fuzz/guide.html#cfgfuzzing_repro), so it was quite puzzling when it didn't seem...
Running the following fails, while it would succeed were I using a normal `cargo run`. ```sh cargo +nightly fuzz run my_fuzz_target --features=foo --features=bar ``` I know I can just combine...
The reason for this is sometimes I only want to fuzz the specific part of code, and don't want to fuzz the whole Rust crate stack.
Here's what happens today if you run `cargo fuzz add my-fuzzer` in a new project: ``` ; cargo fuzz add decompressor Error: could not read the manifest file: /home/jnelson/work/redacted/fuzz/Cargo.toml Caused...
Often, running `cargo fuzz cmin` multiple times yields a smaller corpus each time. It'd be nice to have a command-line option to repeat the process until it no longer made...
cargo 1.80.0-nightly (05364cb2f 2024-05-03) now throws the following clippy error: ``` error: unexpected `cfg` condition name: `fuzzing` --> neqo-transport/src/lib.rs:21:7 | 21 | #[cfg(fuzzing)] | ^^^^^^^ | = help: expected names...
In `cargo-fuzz` 0.12.0, there is an option `--build-std` which has the following help text: ``` --build-std Pass -Zbuild-std to Cargo, which will build the standard library with all the build...
The use case here would be fuzzing some unsafe heavy code to find a corpus that should see a wide variety of inputs, then running the fuzzer, feeding each corpus...
