Update AFL to 0.4 #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This yields an enormous speed boost (almost 10x more exections per second on my machine)
|
Note: Currently, any fuzzers using the LLVM |
a temporary workaround was pushed to afl.rs regarding this: rust-fuzz/afl.rs#144 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates the
aflcrate to version 0,4, which allows us to take advantage of thefuzz!()macro. This macro enables AFL persistent mode, which yielded an almost 10x speed increase on my machine (~3k executions per second -> ~30k executions per second).I've almost added
Cargo.lockto the repository, sinceroughenough-fuzzis a binary (as opposed to a library).To prevent
cargo afl buildfrom trying to compile the honggfuzz target, I've added an explicitafl_targetbinary toCargo.toml. The README has been updated accordingly.