Closed zyh1121 closed 4 years ago
Or, we could just follow the list in install_manifest.txt
/usr/local/lib/klee/runtime/klee-uclibc.bca
/usr/local/lib/klee/runtime/klee-uclibcxx.bca
/usr/local/include/klee/klee.h
/usr/local/lib/klee/runtime/kleeRuntimeIntrinsic.bc
/usr/local/lib/klee/runtime/klee-libc.bc
/usr/local/lib/klee/runtime/libkleeRuntimePOSIX.bca
/usr/local/lib/libkleeRuntest.so.1.0
/usr/local/lib/libkleeRuntest.so
/usr/local/bin/gen-random-bout
/usr/local/bin/kleaver
/usr/local/bin/klee
/usr/local/bin/klee-replay
/usr/local/bin/klee-stats
/usr/local/bin/ktest-tool
/usr/local/bin/converter
and copy those files to the specified locations?
If so, I could find all files except klee.h
. Please advise if this is the correct approach to install the customized KLEE. If so, where could I locate klee.h
?
Thanks again!
ok. I just figured out we may not need to install KLEE globally. It seems the fuzzer will use a local copy specified by the config. thanks
Thanks for releasing the code and this looks very interesting!
I have a question regarding the KLEE part. I saw the KLEE binaries have already been build in the
KLEE
folder. Are we supposed to use the pre-built version in our installation? If so, is it correct to just do amake install
according to https://github.com/evanmak/savior-source/blob/master/Docker/build_savior.sh#L162-L169?I tried that. But it failed because of the missing
CMakeLists.txt
. Any suggestions?Thanks again!!