diff options
| author | van Hauser <vh@thc.org> | 2019-06-25 12:08:50 +0200 |
|---|---|---|
| committer | van Hauser <vh@thc.org> | 2019-06-25 12:08:50 +0200 |
| commit | 5dfb3ded174a6010d9562b0bbddff9aa5f450ff8 (patch) | |
| tree | b73f23fca7d14538159e0ebddc13f2d8122f2edc /docs/perf_tips.txt | |
| parent | 0104e99caabd83e7d53f7b1248425991f4c0c431 (diff) | |
| download | afl++-5dfb3ded174a6010d9562b0bbddff9aa5f450ff8.tar.gz | |
improved documentation
Diffstat (limited to 'docs/perf_tips.txt')
| -rw-r--r-- | docs/perf_tips.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/perf_tips.txt b/docs/perf_tips.txt index 263065c0..215895b6 100644 --- a/docs/perf_tips.txt +++ b/docs/perf_tips.txt @@ -64,6 +64,14 @@ that can offer huge benefits for programs with high startup overhead. Both modes require you to edit the source code of the fuzzed program, but the changes often amount to just strategically placing a single line or two. +If there are important data comparisons performed (e.g. strcmp(ptr, MAGIC_HDR) +then using laf-intel (see llvm_mode/README.laf-intel) will help afl-fuzz a lot +to get to the important parts in the code. + +If you are only intested in specific parts of the code being fuzzed, you can +whitelist the files that are actually relevant. This improves the speed and +accuracy of afl. See llvm_mode/README.whitelist + 4) Profile and optimize the binary ---------------------------------- |