-
-
Notifications
You must be signed in to change notification settings - Fork 293
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
Mutational Push Stage #356
Conversation
no_std build fails... |
This is far from being done :D |
@vanhauser-thc this allows us to build custom mutators for afl++ using libafl, btw :) |
will look tomorrow |
@domenukk PushStage seems to not be a Stage at all, why don't we think to another name? FuzzIterator? |
apart the name, the code lgtm |
Why not a stage? |
* initial commit for push stage * cleanup, no_std, clippy * clippy * fuzzes * readme * fmt
This PR will (eventually) create a Mutational Push Stage that doesn't call an executor for each generated input, but instead returns the next testcase as iterator.
The caller of the push stage must make sure they execute the returned testcase, and that their harness populates the observers, as well as the
exit_kind
.