RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2025-02-15 08:19:51 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

[libFuzzer] minor docs update

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@286299 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Kostya Serebryany 2016-11-08 21:57:37 +00:00
parent 92bee0fe98
commit 9a9bc142bf
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/LibFuzzer.rst
View File

@ -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).