diff options
author | van Hauser <vh@thc.org> | 2024-08-22 18:30:28 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-08-22 18:30:28 +0200 |
commit | 30df52cd8ccd6c4bea05932c8d59875872b04812 (patch) | |
tree | 9e5cacb57ca39b7a428d22fb999e2e2f54040b29 /src/afl-fuzz-init.c | |
parent | 097828391530c7858ba80024d69c4efdad2e2fb2 (diff) | |
parent | d7c99007ffda6846df85da79f55be7522d34b12a (diff) | |
download | afl++-30df52cd8ccd6c4bea05932c8d59875872b04812.tar.gz |
Merge pull request #2193 from ncoghlan/core-dump-notice-rewording
Offer more explicit core dump handling tip
Diffstat (limited to 'src/afl-fuzz-init.c')
-rw-r--r-- | src/afl-fuzz-init.c | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/src/afl-fuzz-init.c b/src/afl-fuzz-init.c index 4f366b0d..10951300 100644 --- a/src/afl-fuzz-init.c +++ b/src/afl-fuzz-init.c @@ -2443,20 +2443,19 @@ 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 just experimenting, 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"); + " echo core | sudo tee /proc/sys/kernel/core_pattern\n"); if (!getenv("AFL_I_DONT_CARE_ABOUT_MISSING_CRASHES")) { |