diff options
author | van Hauser <vh@thc.org> | 2021-03-24 18:19:13 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-03-24 18:19:13 +0100 |
commit | 6e2a0ef233fc09e8751e2d4cba3298610d8bed2c (patch) | |
tree | 0c04cd932d129b45e31fd17c328844295677ca5f /docs/env_variables.md | |
parent | 7dc48478698ba73eeb045af3ca25e4a62e68b359 (diff) | |
parent | 958436be4ba057e8409787e7ff4ddcfa095c46da (diff) | |
download | afl++-6e2a0ef233fc09e8751e2d4cba3298610d8bed2c.tar.gz |
Merge branch 'replay' into tmp
Diffstat (limited to 'docs/env_variables.md')
-rw-r--r-- | docs/env_variables.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/env_variables.md b/docs/env_variables.md index 409425f1..de6b4bd8 100644 --- a/docs/env_variables.md +++ b/docs/env_variables.md @@ -424,6 +424,15 @@ 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. + - 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. |