[llvm-bugs] [Bug 31583] New: libFuzzer shouldn't disable default mutators when a custom one is defined

[via llvm-bugs]

https://llvm.org/bugs/show_bug.cgi?id=31583

            Bug ID: 31583
           Summary: libFuzzer shouldn't disable default mutators when a
                    custom one is defined
           Product: new-bugs
           Version: trunk
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: ttaubert at mozilla.com
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

Currently, libFuzzer disables all default mutators and only the custom mutator,
if one is defined. We're currently applying the patch below to get the default
ones back when building against libFuzzer:

> diff --git libFuzzer/FuzzerMutate.cpp libFuzzer/FuzzerMutate.cpp
> --- libFuzzer/FuzzerMutate.cpp
> +++ libFuzzer/FuzzerMutate.cpp
> @@ -52,10 +52,9 @@
>      DefaultMutators.push_back(
>          {&MutationDispatcher::Mutate_AddWordFromTORC, "CMP"});
> 
> +  Mutators = DefaultMutators;
>    if (EF->LLVMFuzzerCustomMutator)
>      Mutators.push_back({&MutationDispatcher::Mutate_Custom, "Custom"});
> -  else
> -    Mutators = DefaultMutators;
> 
>    if (EF->LLVMFuzzerCustomCrossOver)
>      Mutators.push_back(

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170109/1687a3e1/attachment.html>