Yushan
@strongcourage You could try using the `./afl-cov --help` for more information. Here is what I found to run my test case (`LAVA-M`): `./afl-cov -d ../output/fast_uniq/ -e "cat AFL_FILE | ./uniq...
Hi guys, you need to change arguments in this part `"cat AFL_FILE | LD_LIBRARY_PATH=./lib/.libs ./bin/.libs/somebin -a -b -c"`. This refers to the binary with coverage, which you want to test.
`cat AFL_FILE` should not be changed, `LD_LIBRARY_PATH=xxx` is the library path (you may don't need it), `./bin/xxx/your_binary -a -b -c` is the arguments that you use on AFL after the...
@jdwoolc How is the result with the hints I gave earlier in this thread? Make sure you pass the binary with coverage support only (you don't need the one instrumented...
Why do I need to add `@@`? I thought it is part of git comments so didn't add it. It is better if you could stress on it.
It crashes again with `@@`, and has a new error with `stdin`. I have no idea how I should change the directory. ```` root@f8a44c8e576a:/angora# ./angora_fuzzer -i ../data/base64/fuzzer_input/ -o /root/output/base64 -j...
I used the standard `fuzzer_input` folder provided by `LAVA-M`, and it is located in `xxx/lava_corpus/LAVA-M/base64/fuzzer_input` (the dataset is downloaded with [this](/AngoraFuzzer/Angora/blob/master/docs/lava.md) link in this repo). Here are other environment details:...
And my compiled `base64.tt` has `segmenationt fault` error. I followed all the[ same commands](/AngoraFuzzer/Angora/blob/master/docs/lava.md) to compile this binary. ```` yushanzhang@ubuntu:~/fuzzing/angora$ USE_TRACK=1 bin/angora-clang base64.bc -o base64.tt angora-llvm-pass [+] Track Mode. ModName:...
Seems the crashpoint is part of the sanitizer check: ```` (gdb) r Starting program: /home/yushanzhang/fuzzing/angora/base64.tt [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Program received signal SIGSEGV, Segmentation...