Randomize scheduler/mutator for secondary instances#1
Randomize scheduler/mutator for secondary instances#1wizche wants to merge 1 commit intofekir:masterfrom
Conversation
When starting a slave instance it randomly select a power scheduler and if to use the MOpt mutator (`-L 0`)
|
Hello @wizche , thank you for your PR. I just looked at the man page of afl (never used the scheduler), AFAIK the parameter you added can be passed to the main instance too, correct? Edit: for clarification I'm asking because the intent of afl-pfuzz is to be as thin as possible. Even the help of afl-pfuzz is a wrapper around afl-fuzz, and parameter parsing tries to ignore everything that it does not care about. I currently see no reason why the caller of afl-pfuzz could not provide -p scheduler (as as far I understood its supported by the master too), this way afl-pfuzz remains compatible with the original afl, and does not need to know what scheduler are actually implemented. |
When starting a slave instance it randomly select a power scheduler and if to use the MOpt mutator (
-L 0)