Mopt fuzzing strategy

[selfbypass]

Hi,
Reading the paper, I found that you applied the Mopt fuzzing strategy into VirtFuzz. But I can't find it in codes.

I just found these three mutators. So how does VirtFuzz apply it?

[eknoes]

Hi!
Indeed you are right. I just searched through the commits of our internal repository, and it seems we have accidentally replaced it with the StdScheduledMutator while cleaning up and upgrading some libraries.

See the diff for fuzz/src/main.rs:743:

-        let std_mutator = StdMOptMutator::new(
-            &mut state,
-            havoc_mutations(),
-            6,
-            5,
-        )
-        .unwrap();
+        let std_mutator = StdScheduledMutator::new(havoc_mutations());

When I have time, I'll add an option to the fuzzer to choose between the different mutators. Thanks for pointing that out!

[selfbypass]

Hi! Indeed you are right. I just searched through the commits of our internal repository, and it seems we have accidentally replaced it with the StdScheduledMutator while cleaning up and upgrading some libraries.

See the diff for fuzz/src/main.rs:743:

-        let std_mutator = StdMOptMutator::new(
-            &mut state,
-            havoc_mutations(),
-            6,
-            5,
-        )
-        .unwrap();
+        let std_mutator = StdScheduledMutator::new(havoc_mutations());

When I have time, I'll add an option to the fuzzer to choose between the different mutators. Thanks for pointing that out!

Thanks. It works.