From e1bd9fc6ac4fab8d4f9ba5fd1970c0275ff984b9 Mon Sep 17 00:00:00 2001 From: vanhauser-thc Date: Tue, 12 Nov 2024 14:08:41 +0100 Subject: [PATCH] update docs on asan instances --- docs/fuzzing_in_depth.md | 3 +++ 1 file changed, 3 insertions(+) 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