Offer more explicit core dump handling tip

This commit is contained in:
Alyssa Coghlan
2024-08-21 19:02:38 +10:00
committed by GitHub
parent 0978283915
commit 2b7aae66b6

View File

@ -2443,20 +2443,24 @@ void check_crash_handling(void) {
SAYF(
"\n" cLRD "[-] " cRST
"Hmm, your system is configured to send core dump notifications to an\n"
"Your system is configured to send core dump notifications to an\n"
" external utility. This will cause issues: there will be an "
"extended delay\n"
" between stumbling upon a crash and having this information "
"relayed to the\n"
" fuzzer via the standard waitpid() API.\n"
" If you're just testing, set "
" If you're experimenting (so missed crashes don't matter), set "
"'AFL_I_DONT_CARE_ABOUT_MISSING_CRASHES=1'.\n\n"
" To avoid having crashes misinterpreted as timeouts, please log in "
"as root\n"
" and temporarily modify /proc/sys/kernel/core_pattern, like so:\n\n"
" To avoid having crashes misinterpreted as timeouts, please \n"
" temporarily modify /proc/sys/kernel/core_pattern, like so:\n\n"
" echo core >/proc/sys/kernel/core_pattern\n");
" core_cmd=\"$(cat /proc/sys/kernel/core_pattern)\"\n"
" echo core | sudo tee /proc/sys/kernel/core_pattern\n"
" After fuzz testing is complete, restore the core handling:\n\n"
" echo \"$core_cmd\" | sudo tee /proc/sys/kernel/core_pattern\n");
if (!getenv("AFL_I_DONT_CARE_ABOUT_MISSING_CRASHES")) {