| commit | 5150e2f98e0478d1ea122c5f1e9f1f5564fe882d | [log] [tgz] |
|---|---|---|
| author | Jeff Vander Stoep <[email protected]> | Fri Feb 17 10:00:29 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Fri Feb 17 10:00:29 2023 +0000 |
| tree | fc2c8040d113c87472daf3a99fa770b4ad1f5c8c | |
| parent | 79820b38ced706a498e2a55dc802e9b4e78e6975 [diff] | |
| parent | 0af10c1f249c3b3a3539620f6b486954f9d7183a [diff] |
Upgrade libfuzzer-sys to 0.4.6 am: 6a8c28f9fa am: 0af10c1f24 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/libfuzzer-sys/+/2440375 Change-Id: Ib513f119c0f3838ab58cb55e5bbab77336b271fd 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.