Open dillonfranke opened 9 months ago
It seems that your fpicker doesn't find the shared memory created by AFL++ as the log shows fpicker: [JS]: [*] afl_area_ptr: 0x0
.
Did you enable the option CFLAGS="-DUSEMMAP=1"
when you compile your AFL++?
Yes I did indeed compile AFL++ with CFLAGS="-DUSEMMAP=1"
:/
Hi @ttdennis,
Let me just start by saying thank you for such a cool idea! I'm excited to use this for some fuzzing research I am performing. However, I've been running into an issue when trying to use
fpicker
to perform instrumentation while fuzzing with AFL++.I'm trying to fuzz a function within the
CoreAudio
MacOS library that handles incoming mach messages.Here's the command I'm running:
sudo afl-fuzz -i in -o out -- ./fpicker -v --fuzzer-mode afl --communication-mode shm -e attach -p coreaudiod -f harness.js
Here's my harness.js file before compiling it with
frida-compile
:However,
fpicker
stalls during the first test case, every time. Am I using the tool wrong? Any ideas? Thanks so much:I dug into the logs a bit more and saw this output. It seems to be waiting for a semaphore to be released that never is: