-
Notifications
You must be signed in to change notification settings - Fork 105
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
Rethink API #31
Comments
Another idea here. Something like #[fuzz]
fn test_fuzz(bytes: Vec<u8>) {
...
} which can be invoked with something like |
Nice! even simpler, I love it. On Sat, Apr 23, 2016 at 11:44 AM, Corey Farwell [email protected]
"I disapprove of what you say, but I will defend to the death your right to |
Note to future self: rust-quickcheck implements a |
The library code is now a lot simpler, does not use macros and gives users a lot more control. This solves cargo-fuzz's issue rust-fuzz/cargo-fuzz#101 This syntax is also very similar to the one in AFL.rs. Maybe we should converge to a compatible API? rust-fuzz/afl.rs#31
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
Would be nice to make this library simpler to use. I've been thinking an API like this:
inputted_string
would be aString
. the closure insideafl::run
is the only thing that gets run upon every subsequent call by AFL using the deferred init strategyThe text was updated successfully, but these errors were encountered: