Released YYYY-MM-DD.
- Bindings to
LLVMFuzzerCustomCrossOver
through thefuzz_crossover
macro. example_crossover
using bothfuzz_mutator
andfuzz_crossover
(adapted from @rigtorp)
- Updated to
libFuzzer
commit3747cde5e84f
(release/18.x
).
- TODO (or remove section if none)
- TODO (or remove section if none)
- TODO (or remove section if none)
- TODO (or remove section if none)
Released 2023-08-10.
- Added the
link_libfuzzer
cargo feature. This feature is on by default and preserves the existing behavior of statically linking libfuzzer. You can disable it if you are linking your own version of libfuzzer some other way, or another library that provides the same ABI as libfuzzer.
Released 2023-01-26.
- Fixed a potential name conflict in functions generated by the
fuzz_target!
macro. - Fixed potential stale builds when updating custom libfuzzers to link against.
Released 2022-10-18.
- Added the ability to tell libfuzzer whether to keep files inputs in the corpus
or not. See the
Corpus
type and extended documentation for thefuzz_target!
macro for details.
- Ensured that there is always at least one inline-never frame on the stack per fuzz target. This helps prevent oss-fuzz from "deduplicating" different bugs from different fuzz targets into the same bug.
Released 2022-09-01.
- Updated to
libFuzzer
commitdf90d22
(release/15.x
). - LLVM 16's upcoming change to build requirements to C++17
necessitate reflecting those changes. (
libFuzzer
updates contain C++14 code) - Drastically reduce build times by using parallel C++ compilation jobs
- Updated
rand
dependency from 0.8.3 to 0.8.5 - Updated
flate2
dependency from 1.0.20 to 1.0.24
Released 2020-03-03.
- Updated to
libFuzzer
commit60e32a1
.
- Fixed an issue where the
fuzz_target!
macro would sometimes expand to versions of itself that were not$crate
prefixed and would result in "error: cannot find macrofuzz_target
in this scope" if the caller didn't import the macro but used the qualified version of it instead.
Released 2020-05-26.
- Improved performance of checking for whether
cargo fuzz
is requesting thestd::fmt::Debug
output of an input or not. This is always false during regular fuzzing, so making this check faster should give slightly better fuzzing throughput.
Released 2020-05-13.
- Added support for defining custom mutators. See the documentation for the
fuzz_mutator!
macro for details.
- Upgraded libfuzzer to llvm/llvm-project's 70cbc6d.
Released 2021-02-24.
- The public
arbitrary
dependency was updated to version 1.0.
Released 2020-11-18.
Released 2020-08-22.
- Updated
arbitrary
dependency to 0.4.6
Released 2020-07-27.
-
Upgraded libfuzzer to commit 4a4cafa.
Notably, this pulls in the new Entropic engine for libFuzzer, which should boost fuzzing efficiency when enabled. You can enable Entropic by passing
-entropic=1
to your built fuzz targets (although, note that it is still labeled "experimental").
Released 2020-03-18.
- Upgraded the
arbitrary
dependency re-export to version 0.4.1.
Released 2020-02-27.
- Fixed a fuzzing performance issue where libfuzzer could unnecessarily spend
time exploring all the ways that an
Arbitrary
implementation could fail to construct an instance of itself because the fuzzer provided too few bytes. See rust-fuzz#59 for details.
Released 2019-01-22.
- Now works with and re-exports
arbitrary
versions 0.4.x.
Released 2019-01-16.
- Added support for the
CUSTOM_LIBFUZZER_STD_CXX=<lib>
environment variable during builds that already use a custom libFuzzer checkout withCUSTOM_LIBFUZZER_PATH
. This allows you to explicitly choose to link LLVM or GNU C++ standard libraries.
Released 2020-01-14.
- Using
arbitrary
0.3.x now. It is re-exported aslibfuzzer_sys::arbitrary
.
- You can enable support for
#[derive(Arbitrary)]
with the"arbitrary-derive"
cargo feature. This is a synonym for thearbitrary
crate's"derive"
cargo feature.