diff options
| author | Andrea Fioraldi <andreafioraldi@gmail.com> | 2020-02-03 13:02:16 +0100 |
|---|---|---|
| committer | Andrea Fioraldi <andreafioraldi@gmail.com> | 2020-02-03 13:02:16 +0100 |
| commit | e2eedefc65bec1a04605f117a11ca8bdf9d80323 (patch) | |
| tree | 653e28fb2f74790ff35706c9c93ce91893f5a3a2 /src | |
| parent | fd03c64346ab3f63fc5ceafd891dee245121b5c9 (diff) | |
| download | afl++-e2eedefc65bec1a04605f117a11ca8bdf9d80323.tar.gz | |
docs to md
Diffstat (limited to 'src')
| -rw-r--r-- | src/afl-fuzz-init.c | 2 | ||||
| -rw-r--r-- | src/afl-fuzz.c | 2 | ||||
| -rw-r--r-- | src/afl-gotcpu.c | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/src/afl-fuzz-init.c b/src/afl-fuzz-init.c index c4a02698..e39480da 100644 --- a/src/afl-fuzz-init.c +++ b/src/afl-fuzz-init.c @@ -1719,7 +1719,7 @@ void get_core_count(void) { } else if (cur_runnable + 1 <= cpu_core_count) { - OKF("Try parallel jobs - see %s/parallel_fuzzing.txt.", doc_path); + OKF("Try parallel jobs - see %s/parallel_fuzzing.md.", doc_path); } diff --git a/src/afl-fuzz.c b/src/afl-fuzz.c index eae4ba1f..4957a8bf 100644 --- a/src/afl-fuzz.c +++ b/src/afl-fuzz.c @@ -133,7 +133,7 @@ static void usage(u8* argv0) { "Other stuff:\n" " -T text - text banner to show on the screen\n" - " -M / -S id - distributed mode (see parallel_fuzzing.txt)\n" + " -M / -S id - distributed mode (see parallel_fuzzing.md)\n" " -I command - execute this command/script when a new crash is " "found\n" " -B bitmap.txt - mutate a specific test case, use the out/fuzz_bitmap " diff --git a/src/afl-gotcpu.c b/src/afl-gotcpu.c index 5be30238..214862a9 100644 --- a/src/afl-gotcpu.c +++ b/src/afl-gotcpu.c @@ -19,7 +19,7 @@ This tool provides a fairly accurate measurement of CPU preemption rate. It is meant to complement the quick-and-dirty load average widget shown - in the afl-fuzz UI. See docs/parallel_fuzzing.txt for more info. + in the afl-fuzz UI. See docs/parallel_fuzzing.md for more info. For some work loads, the tool may actually suggest running more instances than you have CPU cores. This can happen if the tested program is spending |