Got error when I tried to fuzz the target_programs just like examples

[0n3t04ll]

After finished install all the dependent python library, I tried to fuzz the binary in target_programs just like the examples, and I got this error:

WARNING | 2018-06-07 09:19:28,663 | angr.engines.successors | Exit state has over 257 possible solutions. Likely unconstrained; skipping. <BV32 global_c000013_64_32{UNINITIALIZED}>
Deprecation warning: Use main_object instead of main_bin
WARNING | 2018-06-07 09:19:31,096 | fuzzer.fuzzer | not forced
Traceback (most recent call last):
File "./TFuzz", line 64, in
main()
File "./TFuzz", line 55, in main
tfuzzsys.run()
File "/home/starpt/Documents/T-Fuzz/tfuzz/tfuzz_sys.py", line 160, in run
if not self.__fuzz_one_program():
File "/home/starpt/Documents/T-Fuzz/tfuzz/tfuzz_sys.py", line 139, in __fuzz_one_program
self.__current_fuzzer.start()
File "/home/starpt/Documents/T-Fuzz/tfuzz/tfuzz_fuzzer.py", line 88, in start
self._fuzzer.start()
File "/home/starpt/.virtualenvs/t-fuzz/local/lib/python2.7/site-packages/fuzzer/fuzzer.py", line 232, in start
self._start_afl()
File "/home/starpt/.virtualenvs/t-fuzz/local/lib/python2.7/site-packages/fuzzer/fuzzer.py", line 543, in _start_afl
master = self._start_afl_instance() # the master fuzzer
File "/home/starpt/.virtualenvs/t-fuzz/local/lib/python2.7/site-packages/fuzzer/fuzzer.py", line 535, in _start_afl_instance
return subprocess.Popen(args, stdout=fp, close_fds=True)
File "/usr/lib/python2.7/subprocess.py", line 711, in init
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

I guessed it happened because I didn't export the AFL_PATH environment, so I tried to:
export AFL_PATH=~/.virtualenvs/t-fuzz/bin, and I got same error again......

How should I do to fixed this problem? Thank you

[benquike]

@0n3t04ll Thanks for your feedback. Please give us some time, we are doing more tests and will look at this issue later.

[chubbymaggie]

I had the same issue
I think its due shellphish-afl. I had some issues in applying AFL patch. So, manually built shellphish-afl, instead of pip install, disabling the patch.

[dukebarman]

I have same error. OS: Debian 9.4

[benquike]

@0n3t04ll @chubbymaggie @dukebarman I am having another guy testing it in a new environment.
But the environment I tested it was Ubuntu 16.04. I will mention it in the documents.

Please wait for a little more.

[dukebarman]

No problem ;) I tested on Ubuntu 18 and Debian 9 with last updates

[fouzhe]

I had the same issue
I think its due shellphish-afl. I had some issues in applying AFL patch. So, manually built shellphish-afl, instead of pip install, disabling the patch.

How to build shellphish-afl manually?
Thanks!

[fouzhe]

I had the same issue
I think its due shellphish-afl. I had some issues in applying AFL patch. So, manually built shellphish-afl, instead of pip install, disabling the patch.

How to build shellphish-afl manually?
Thanks!

I've solved this issue by installing shellphish-afl using following command:

pip install git+https://github.com/shellphish/shellphish-afl

Thanks!