diff options
| author | vanhauser-thc <vh@thc.org> | 2024-11-12 14:08:41 +0100 |
|---|---|---|
| committer | vanhauser-thc <vh@thc.org> | 2024-11-15 09:48:34 +0100 |
| commit | e1bd9fc6ac4fab8d4f9ba5fd1970c0275ff984b9 (patch) | |
| tree | 31f5dc5b38653abdf3bc641381c397965fa0400b | |
| parent | 2c6f2c970dd26d01007c0329e1a10eed7ded89c2 (diff) | |
| download | afl++-e1bd9fc6ac4fab8d4f9ba5fd1970c0275ff984b9.tar.gz | |
update docs on asan instances
| -rw-r--r-- | docs/fuzzing_in_depth.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/fuzzing_in_depth.md b/docs/fuzzing_in_depth.md index 79d0500d..14682489 100644 --- a/docs/fuzzing_in_depth.md +++ b/docs/fuzzing_in_depth.md @@ -201,6 +201,9 @@ type. This is enough because e.g. a use-after-free bug will be picked up by ASAN (address sanitizer) anyway after syncing test cases from other fuzzing instances, so running more than one address sanitized target would be a waste. +*IF* you are running a saturated corpus, then you can run up to half of the +instances with sanitizers. + The following sanitizers have built-in support in AFL++: * ASAN = Address SANitizer, finds memory corruption vulnerabilities like |