target compile issues about nestfuzz

[vanhauser-thc]

here compiled with debug:

#15 0x00007ffff7fbb68d (anonymous namespace)::LoopHandlingPass::visitExploitation(llvm::Instruction*) /prg/NestFuzz/ipl-modeling/pass/LoopHandlingPass.cpp:649:5
#17 0x00007ffff7fb93be (anonymous namespace)::LoopHandlingPass::visitCallInst(llvm::Instruction*) /prg/NestFuzz/ipl-modeling/pass/LoopHandlingPass.cpp:507:15
#18 0x00007ffff7fb93be (anonymous namespace)::LoopHandlingPass::runOnModule(llvm::Module&) /prg/NestFuzz/ipl-modeling/pass/LoopHandlingPass.cpp:949:11

[Mech0n]

Sorry for the late reply. I tried the following compilation cmd, But not reproduce the bug.

CC=.../test-clang CXX=.../test-clang++ ./configure
make -j

I compiled successfully.

[vanhauser-thc]

@Mech0n did you try with https://github.com/vanhauser-thc/fuzzing-targets/raw/master/tiff-4.0.4.zip or a newer version?

[Mech0n]

Sorry about that.
I tried the version or compression package you provided and I compiled successfully.

➜  tiff-4.0.4 ls tools
tiffsplit ....

➜  libtiff eva/fuzzer/NestFuzz/ipl-modeling/install/test-clang  -DHAVE_CONFIG_H -I. -g -Wall -W -MT tif_close.lo -MD -MP -MF .deps/tif_close.Tpo -c tif_close.c -o tif_close.o
use_zlib: (null)
clang -DHAVE_CONFIG_H -I. -g -Wall -W -MT tif_close.lo -MD -MP -MF .deps/tif_close.Tpo -c tif_close.c -o tif_close.o -Xclang -load -Xclang eva/fuzzer/NestFuzz/ipl-modeling/install/pass/libLoopHandlingPass.so -mllvm -chunk-exploitation-list=eva/fuzzer/NestFuzz/ipl-modeling/install/rules/exploitation_list.txt -Xclang -load -Xclang eva/fuzzer/NestFuzz/ipl-modeling/install/pass/libDFSanPass.so -mllvm -chunk-dfsan-abilist=eva/fuzzer/NestFuzz/ipl-modeling/install/rules/angora_abilist.txt -mllvm -chunk-dfsan-abilist=eva/fuzzer/NestFuzz/ipl-modeling/install/rules/dfsan_abilist.txt -pie -fpic -Qunused-arguments -fno-discard-value-names -g -O0
➜  libtiff file tif_close.o
tif_close.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), with debug_info, not stripped

Maybe you need to wait for configure to check . I've been through a similar wait before, like waiting for checking mmap .

Did you compile the llvm or just apt install it ?

[vanhauser-thc]

I found out why this is an issue. I compiled llvm-10 myself but I compiled it in Debug, not Release. If I compile it in Release mode then I do not encounter this issue.