about summary refs log tree commit diff
path: root/docs/env_variables.md
diff options
context:
space:
mode:
authorvan Hauser <vh@thc.org>2021-03-25 08:54:21 +0100
committerGitHub <noreply@github.com>2021-03-25 08:54:21 +0100
commit3b860c1dd63036ee99fbb548c5c0ba0c67f9af08 (patch)
tree66d0555fbe862fdbe083450f6fe087bd72945bd7 /docs/env_variables.md
parentd319b4a3819052de5bf576c560da6e4687c31de9 (diff)
parentab394836a9fe3faadb9d1af3a7d377bbcf5b5eee (diff)
downloadafl++-3b860c1dd63036ee99fbb548c5c0ba0c67f9af08.tar.gz
Merge pull request #844 from AFLplusplus/replay
AFL_PERSISTENT_RECORD support
Diffstat (limited to 'docs/env_variables.md')
-rw-r--r--docs/env_variables.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/env_variables.md b/docs/env_variables.md
index 409425f1..6d3d1714 100644
--- a/docs/env_variables.md
+++ b/docs/env_variables.md
@@ -424,6 +424,16 @@ checks or alter some of the more exotic semantics of the tool:
   - Setting `AFL_FORCE_UI` will force painting the UI on the screen even if
     no valid terminal was detected (for virtual consoles)
 
+  - If you are using persistent mode (you should, see [instrumentation/README.persistent_mode.md](instrumentation/README.persistent_mode.md))
+    some targets keep inherent state due which a detected crash testcase does
+    not crash the target again when the testcase is given. To be able to still
+    re-trigger these crashes you can use the `AFL_PERSISTENT_RECORD` variable
+    with a value of how many previous fuzz cases to keep prio a crash.
+    if set to e.g. 10, then the 9 previous inputs are written to
+    out/default/crashes as RECORD:000000,cnt:000000 to RECORD:000000,cnt:000008
+    and RECORD:000000,cnt:000009 being the crash case.
+    NOTE: This option needs to be enabled in config.h first!
+
   - If you are Jakub, you may need `AFL_I_DONT_CARE_ABOUT_MISSING_CRASHES`.
     Others need not apply, unless they also want to disable the
     `/proc/sys/kernel/core_pattern` check.