| Index: third_party/afl/src/llvm_mode/README.llvm
|
| diff --git a/third_party/afl/src/llvm_mode/README.llvm b/third_party/afl/src/llvm_mode/README.llvm
|
| index f3789e2bb9ed5edae056200f6d2d66cea749b911..f7d48c9129880eab4b3f27e48131a8e917290ede 100644
|
| --- a/third_party/afl/src/llvm_mode/README.llvm
|
| +++ b/third_party/afl/src/llvm_mode/README.llvm
|
| @@ -161,11 +161,6 @@ do not fully reset the critical state, you may end up with false positives or
|
| waste a whole lot of CPU power doing nothing useful at all. Be particularly
|
| wary of memory leaks and of the state of file descriptors.
|
|
|
| -When running in this mode, the execution paths will inherently vary a bit
|
| -depending on whether the input loop is being entered for the first time or
|
| -executed again. To avoid spurious warnings, the feature implies
|
| -AFL_NO_VAR_CHECK and hides the "variable path" warnings in the UI.
|
| -
|
| PS. Because there are task switches still involved, the mode isn't as fast as
|
| "pure" in-process fuzzing offered, say, by LLVM's LibFuzzer; but it is a lot
|
| faster than the normal fork() model, and compared to in-process fuzzing,
|
|
|