Add support for defining custom mutators #79
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See the doc comments for the
fuzz_mutator!
macro for example usage and user-level information.There is some slightly funky stuff going on with
data
,size
, andmax_size
that doesn't feel 100% Rust-y / is a little subtle to support size-aware mutations.data
is basically avec
's heap allocation,size
is basicallyvec.len()
, andmax(size, max_size)
is basicallyvec.capacity()
. Not sure that this API can really be improved upon while remaining a thin wrapper over what libfuzzer gives us (i.e. doesn't introduce a ~fork ofstd::vec::Vec
) but I'm open to ideas!Supersedes #62.