As discussed here ,
AFL_I_DONT_CARE_ABOUT_MISSING_CRASHES flag was added to avoid modifying /proc/sys/kernel/core_pattern in order to start the fuzzing process.
My question is if the AFL_I_DONT_CARE_ABOUT_MISSING_CRASHES flag is set, does AFL really miss out from recording crashes during the fuzzing process (as the name of the flag suggests)? For instance, with this flag set to 1, if a crash takes place during the fuzzing process, would afl increment the crash counter and update the corresponding info in the AFL display graphic, while fuzzing?
If afl does miss out recording crash info with this flag set, is there any way to get the crash data without having to modify core_pattern?
As discussed here ,
AFL_I_DONT_CARE_ABOUT_MISSING_CRASHESflag was added to avoid modifying/proc/sys/kernel/core_patternin order to start the fuzzing process.My question is if the
AFL_I_DONT_CARE_ABOUT_MISSING_CRASHESflag is set, does AFL really miss out from recording crashes during the fuzzing process (as the name of the flag suggests)? For instance, with this flag set to 1, if a crash takes place during the fuzzing process, would afl increment the crash counter and update the corresponding info in the AFL display graphic, while fuzzing?If afl does miss out recording crash info with this flag set, is there any way to get the crash data without having to modify
core_pattern?