about summary refs log tree commit diff
diff options
context:
space:
mode:
authorvan Hauser <vh@thc.org>2021-07-20 22:20:35 +0200
committerGitHub <noreply@github.com>2021-07-20 22:20:35 +0200
commit5543bd5b638fdb9460d8a4b58982d8bd9f59627d (patch)
tree7cb31be63ac35843a76088386d0dd7869bb48698
parenta772fbf1cdaf96dd91c040faa2293b18a10c0fd1 (diff)
parent6a6387582c9a08af49c73e7a29bc85cca0c1a047 (diff)
downloadafl++-5543bd5b638fdb9460d8a4b58982d8bd9f59627d.tar.gz
Merge pull request #1036 from moshekaplan/patch-1
Update README.persistent_mode.md
-rw-r--r--instrumentation/README.persistent_mode.md13
1 files changed, 8 insertions, 5 deletions
diff --git a/instrumentation/README.persistent_mode.md b/instrumentation/README.persistent_mode.md
index 24f81ea0..26c7aa8f 100644
--- a/instrumentation/README.persistent_mode.md
+++ b/instrumentation/README.persistent_mode.md
@@ -2,13 +2,16 @@
 
 ## 1) Introduction
 
-The most effective way is to fuzz in persistent mode, as the speed can easily
+In persistent mode, afl++ fuzzes a target multiple times
+in a single process, instead of forking a new process for each fuzz execution.
+This is the most effective way to fuzz, as the speed can easily
 be x10 or x20 times faster without any disadvanges.
-*All professional fuzzing is using this mode.*
+*All professional fuzzing uses this mode.*
 
-This requires that the target can be called in a (or several) function(s),
-and that its state can be resetted so that multiple calls can be performed
-without resource leaks and former runs having no impact on following runs
+
+Persistent mode requires that the target can be called in one or more functions,
+and that its state can be reset so that multiple calls can be performed
+without resource leaks and earlier runs will have no impact on future runs
 (this can be seen by the `stability` indicator in the `afl-fuzz` UI).
 
 Examples can be found in [utils/persistent_mode](../utils/persistent_mode).