You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2024. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
AftabHussain
changed the title
Regarding AFL_I_DONT_CARE_ABOUT_MISSING_CRASHES
How to get crash data from AFL (without modifying /proc/sys/kernel/core_pattern)?
Jan 6, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
?The text was updated successfully, but these errors were encountered: