search for: libllvmfuzz

...out the fuzzer library and clang-fuzzer, but it doesn't seem to build for me. From the cmake files, I was pretty sure all I need to do is set -DLLVM_USE_SANITIZE_COVERAGE=ON, but with this I get a number of link errors for "lib/Fuzzer/test/LLVMFuzzer-CounterTest", for example: lib/libLLVMFuzzer.a(FuzzerLoop.cpp.o): In function `SetDeathCallback': /home/bogner/code/llvm/lib/Fuzzer/FuzzerLoop.cpp:31: undefined reference to `__sanitizer_set_death_callback' lib/libLLVMFuzzer.a(FuzzerLoop.cpp.o): In function `fuzzer::Fuzzer::SetDeathCallback()': /home/bogner/code/llvm/lib/F...

...stall the LLVM libraries, but that is completely configurable in the build system. It doesn't work for libFuzzer because the CMake build for libFuzzer is not built using any of the LLVM CMake modules or following any of LLVM's conventions. > Thus installations of Clang would not contain libLLVMFuzzer, but we would like them to, so that users would not have > to compile anything, and could just call `clang -fsanitize=fuzzer`. > > That could probably be done with another CMake change, but I have no idea how to do that. Yea, libFuzzer's CMake really needs a big overhaul, and proba...

> On May 9, 2017, at 3:00 PM, Kostya Serebryany <kcc at google.com> wrote: > > Thanks for the explanations! (it was worth asking) > > I do want to build libFuzzer itself (and its tests) using the just-built clang. So, llvm/runtimes then. > I'd name the directory llvm/runtimes/libFuzzer, if possible (the old path was lib/Fuzzer which is how the tool got it's

...le in the build system. It >>> doesn't work for libFuzzer because the CMake build for libFuzzer is not >>> built using any of the LLVM CMake modules or following any of LLVM's >>> conventions. >>> >>> Thus installations of Clang would not contain libLLVMFuzzer, but we >>> would like them to, so that users would not have >>> to compile anything, and could just call `clang -fsanitize=fuzzer`. >>> >>> That could probably be done with another CMake change, but I have no >>> idea how to do that. >>> >...

...ompletely configurable in the build system. It >> doesn't work for libFuzzer because the CMake build for libFuzzer is not >> built using any of the LLVM CMake modules or following any of LLVM's >> conventions. >> >> Thus installations of Clang would not contain libLLVMFuzzer, but we would >> like them to, so that users would not have >> to compile anything, and could just call `clang -fsanitize=fuzzer`. >> >> That could probably be done with another CMake change, but I have no idea >> how to do that. >> >> >> Yea, libFu...

...em. It >>>> doesn't work for libFuzzer because the CMake build for libFuzzer is not >>>> built using any of the LLVM CMake modules or following any of LLVM's >>>> conventions. >>>> >>>> Thus installations of Clang would not contain libLLVMFuzzer, but we >>>> would like them to, so that users would not have >>>> to compile anything, and could just call `clang -fsanitize=fuzzer`. >>>> >>>> That could probably be done with another CMake change, but I have no >>>> idea how to do tha...

...gt;> doesn't work for libFuzzer because the CMake build for libFuzzer is not >>>>> built using any of the LLVM CMake modules or following any of LLVM's >>>>> conventions. >>>>> >>>>> Thus installations of Clang would not contain libLLVMFuzzer, but we >>>>> would like them to, so that users would not have >>>>> to compile anything, and could just call `clang -fsanitize=fuzzer`. >>>>> >>>>> That could probably be done with another CMake change, but I have no >>>>&gt...

...pletely configurable in the build system. It doesn't work for libFuzzer because the CMake build for libFuzzer is not built using any of the LLVM CMake modules or following any of LLVM's conventions. >>>>> >>>>>> Thus installations of Clang would not contain libLLVMFuzzer, but we would like them to, so that users would not have >>>>>> to compile anything, and could just call `clang -fsanitize=fuzzer`. >>>>>> >>>>>> That could probably be done with another CMake change, but I have no idea how to do that. >&g...