|
|
# Issues with core pattern
|
|
|
You should follow the directions suggested by AFL.
|
|
|
```
|
|
|
afl-fuzz 2.52b by <lcamtuf@google.com>
|
|
|
[+] You have 2 CPU cores and 1 runnable tasks (utilization: 50%).
|
|
|
[+] Try parallel jobs - see /usr/share/doc/afl-doc/docs/parallel_fuzzing.txt.
|
|
|
[*] Checking CPU core loadout...
|
|
|
[+] Found a free CPU core, binding to #0.
|
|
|
[*] Checking core_pattern...
|
|
|
|
|
|
[-] Hmm, your system is configured to send core dump notifications to an
|
|
|
external utility. This will cause issues: there will be an extended delay
|
|
|
between stumbling upon a crash and having this information relayed to the
|
|
|
fuzzer via the standard waitpid() API.
|
|
|
|
|
|
To avoid having crashes misinterpreted as timeouts, please log in as root
|
|
|
and temporarily modify /proc/sys/kernel/core_pattern, like so:
|
|
|
|
|
|
echo core >/proc/sys/kernel/core_pattern
|
|
|
|
|
|
[-] PROGRAM ABORT : Pipe at the beginning of 'core_pattern'
|
|
|
Location : check_crash_handling(), afl-fuzz.c:7275
|
|
|
```
|
|
|
|
|
|
# No instrumentation detected
|
|
|
If AFL reports `No instrumented detection`, you must first set the environment variable:
|
|
|
If AFL reports `No instrumentation detected`, you must first set the environment variable:
|
|
|
```
|
|
|
export AFL_SKIP_BIN_CHECK=1
|
|
|
```
|
... | ... | |