Third_party in docker image may need rebuild
Hi prashast, thanks for your great work.
I met a problem while using the docker images. I validated the fuzzers then i got a message Empty/non-existent directory detected for queue folder, please check fuzzer configuration.
So i remove all the dirs under third_third and rebuild the project as the Installing SieveFuzz from scratch. It worked correct.
Maybe there is a problem in the docker image?
I use Arch Linux. I can't determine if this caused the problem.
Hi, thanks for testing out the image! Can you clarify which particular docker image were you testing? Was it the standalone or the artifact image? Also, could you briefly describe the steps that you followed which led to the fuzzer validation failing?
Hi, i test the standalone.
The steps i followed is
beanstalkd &
python3 create_fuzz_script.py -c sanitycheck.config -n 7 --flush
python3 create_fuzz_script.py -c sanitycheck.config -n 7 --flush
python3 create_fuzz_script.py -c sanitycheck.config -n 7 --flush
python3 create_fuzz_script.py -c sanitycheck.config -n 7 --put
python3 create_fuzz_script.py -c sanitycheck.config -n 7 --get
Infact totaly same as the readme. I use ./sanitycheck_run.sh to test.
By the way , I fix the problem by:
cd /root/Sievefuzz/third_party
rm -r sievefuzz spdlog SVF
cd ..
./build.sh
cp gllvm_bins/* third_party/SVF/Release-build/bin/
# Could work without this command
eval/setup_fuzzer_env.sh
While i building the docker image, some errors occur at building the SVF:
Unable to find executable: mta
...
Unable to find executable: cfl
...
Failed to change working directory to /root/sievefuzz/third_party/SVF/-build/bin : No such file or directory
I have not encountered these situations while i followed Installing SieveFuzz from scratch.