-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for AFL Persistent Mode #131
Comments
Maybe you should try cargo-fuzz or honggfuzz-rs. They both use persistent mode. Disclaimer: I'm the author of honggfuzz-rs. |
Also I want to point out that I'm working on making this happen in AFL.rs. |
Performance goes from ~2200/s to 17000/s on my i7-7700HQ while fuzzing the `url_read` target. closes rust-fuzz#131 partially addresses rust-fuzz#31
Done in #137 |
Great Project!
One problem I have is that startup for my binary is pretty slow.
The way I understood it, afl is given the actual binary to execute and will fork on _start.
Since the afl.rs api already wraps every call in a closure, it would map perfectly to Persistent Mode:
https://github.com/mirrorer/afl/blob/master/llvm_mode/README.llvm#L139
That way execution speed (at least the setup) should be a lot quicker.
A good middle ground might be the start the delayed fork server at the rust afl entrypoint.
The text was updated successfully, but these errors were encountered: