From b506466a8a9b609aad1c07289ca54d68b58bcfd9 Mon Sep 17 00:00:00 2001 From: Kostya Serebryany Date: Tue, 8 Nov 2016 21:57:37 +0000 Subject: [libFuzzer] minor docs update llvm-svn: 286299 --- llvm/docs/LibFuzzer.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'llvm/docs/LibFuzzer.rst') diff --git a/llvm/docs/LibFuzzer.rst b/llvm/docs/LibFuzzer.rst index cf49c8def01..a496af26630 100644 --- a/llvm/docs/LibFuzzer.rst +++ b/llvm/docs/LibFuzzer.rst @@ -72,7 +72,7 @@ Like this: } Note that this fuzz target does not depend on libFuzzer in any way -ans so it is possible and even desirable to use it with other fuzzing engines +and so it is possible and even desirable to use it with other fuzzing engines e.g. AFL_ and/or Radamsa_. Some important things to remember about fuzz targets: @@ -81,8 +81,8 @@ Some important things to remember about fuzz targets: * It must tolerate any kind of input (empty, huge, malformed, etc). * It must not `exit()` on any input. * It may use threads but ideally all threads should be joined at the end of the function. -* It must be as deterministic as possible. Non-determinism (e.g. random decisions not based on the input byte) will make fuzzing inefficient. -* It must be fast. Try avoiding cubic or greater complexity. +* It must be as deterministic as possible. Non-determinism (e.g. random decisions not based on the input bytes) will make fuzzing inefficient. +* It must be fast. Try avoiding cubic or greater complexity, logging, or excessive memory consumption. * Ideally, it should not modify any global state (although that's not strict). -- cgit v1.2.3