aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/Changelog.md2
-rw-r--r--docs/life_pro_tips.md3
-rw-r--r--docs/status_screen.md8
3 files changed, 3 insertions, 10 deletions
diff --git a/docs/Changelog.md b/docs/Changelog.md
index aa55fbde..9eb47e18 100644
--- a/docs/Changelog.md
+++ b/docs/Changelog.md
@@ -15,6 +15,8 @@ sending a mail to <afl-users+subscribe@googlegroups.com>.
- afl-llvm/gcc-rt.o merged into afl-compiler-rt.o
- afl-fuzz
- memory limits are now disabled by default, set them with -m if required
+ - deterministic fuzzing is now disabled by default and can be enabled with
+ -D. It is still enabled by default for -M.
- statsd support by Edznux, thanks a lot!
- Marcel Boehme submitted a patch that improves all AFFast schedules :)
- reading testcases from -i now descends into subdirectories
diff --git a/docs/life_pro_tips.md b/docs/life_pro_tips.md
index 0004c297..323f16f1 100644
--- a/docs/life_pro_tips.md
+++ b/docs/life_pro_tips.md
@@ -85,6 +85,3 @@ You can find a simple solution in examples/argv_fuzzing.
Remove the checksum-checking code or use a postprocessor!
See examples/custom_mutators/ for more.
-## Dealing with a very slow target or hoping for instant results?
-
-Specify `-d` when calling afl-fuzz!
diff --git a/docs/status_screen.md b/docs/status_screen.md
index 2eeb8f3f..f7655bf4 100644
--- a/docs/status_screen.md
+++ b/docs/status_screen.md
@@ -86,10 +86,7 @@ Every fuzzing session should be allowed to complete at least one cycle; and
ideally, should run much longer than that.
As noted earlier, the first pass can take a day or longer, so sit back and
-relax. If you want to get broader but more shallow coverage right away, try
-the `-d` option - it gives you a more familiar experience by skipping the
-deterministic fuzzing steps. It is, however, inferior to the standard mode in
-a couple of subtle ways.
+relax.
To help make the call on when to hit `Ctrl-C`, the cycle counter is color-coded.
It is shown in magenta during the first pass, progresses to yellow if new finds
@@ -118,9 +115,6 @@ inputs it decided to ditch because they were persistently timing out.
The "*" suffix sometimes shown in the first line means that the currently
processed path is not "favored" (a property discussed later on).
-If you feel that the fuzzer is progressing too slowly, see the note about the
-`-d` option in this doc.
-
### Map coverage
```