| commit | d9c9674a604b494a2da4d29b0b55d525ae29da2c | [log] [tgz] |
|---|---|---|
| author | Matthew Maurer <[email protected]> | Thu Mar 09 17:04:57 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Thu Mar 09 17:04:57 2023 +0000 |
| tree | fb5f91a0b6ecc9dc0229fad0f71e4c8fdf97d5a9 | |
| parent | 8c743dd36a28c4afcc18bd76a0b27d16c688c61b [diff] | |
| parent | 178ca0741e0a6da521a72b5f63efbe15682a25ac [diff] |
Make libfuzzer-sys available to product and vendor am: f0a3f98be2 am: 7139ba0523 am: 178ca0741e Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/libfuzzer-sys/+/2475946 Change-Id: I28f7cbd39a71f38e11912f7476a2e94d02d00b67 Signed-off-by: Automerger Merge Worker <[email protected]>
libfuzzer-sys CrateBarebones wrapper around LLVM's libFuzzer runtime library.
The CPP parts are extracted from compiler-rt git repository with git filter-branch.
libFuzzer relies on LLVM sanitizer support. The Rust compiler has built-in support for LLVM sanitizer support, for now, it's limited to Linux. As a result, libfuzzer-sys only works on Linux.
cargo fuzz!The recommended way to use this crate with cargo fuzz!.
This crate can also be used manually as following:
First create a new cargo project:
$ cargo new --bin fuzzed $ cd fuzzed
Then add a dependency on the fuzzer-sys crate and your own crate:
[dependencies] libfuzzer-sys = "0.4.0" your_crate = { path = "../path/to/your/crate" }
Change the fuzzed/src/main.rs to fuzz your code:
#![no_main] use libfuzzer_sys::fuzz_target; fuzz_target!(|data: &[u8]| { // code to fuzz goes here });
Build by running the following command:
$ cargo rustc -- \ -C passes='sancov' \ -C llvm-args='-sanitizer-coverage-level=3' \ -C llvm-args='-sanitizer-coverage-inline-8bit-counters' \ -Z sanitizer=address
And finally, run the fuzzer:
$ ./target/debug/fuzzed
./update-libfuzzer.sh <github.com/llvm-mirror/llvm-project SHA1>
All files in libfuzzer directory are licensed NCSA.
Everything else is dual-licensed Apache 2.0 and MIT.