| commit | e9b4f23f4c5e8fd5905ebf7954ac3b6142911841 | [log] [tgz] |
|---|---|---|
| author | Ivan Lozano <ivanlozano@google.com> | Mon Jan 25 21:26:58 2021 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Jan 25 21:26:58 2021 +0000 |
| tree | 20ca241ea27f48740dcbca22ba00bc936bfe82f1 | |
| parent | 1f10a38181fabe47e026630dfb9fc6f6a747f8c6 [diff] | |
| parent | 21394e5719ef32be2160a81abacbb5a0db71cba6 [diff] |
Add metadata and build files for libfuzzer-sys am: 1b0f479bcd am: 2fa1297759 am: 21394e5719 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/libfuzzer-sys/+/1500711 MUST ONLY BE SUBMITTED BY AUTOMERGER Change-Id: I9e047ed82fa5fe005ac6f305c49af239d8fa6172
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.3.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' \ -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.