search for: dllvm_use_sanit

...address) My configuration for building the fuzzers in the LLVM tree doesn't seem to work any more (possibly as of moving libFuzzer to compiler-rt, but there have been a few other changes in the last week or so that may be related). I'm building with a fresh top-of-tree clang and setting -DLLVM_USE_SANITIZER=Address and -DLLVM_USE_SANITIZE_COVERAGE=On, which was working before: % cmake -GNinja \ -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On \ -DLLVM_ENABLE_WERROR=On \ -DLLVM_USE_SANITIZER=Address -DLLVM_USE_SANITIZE_COVERAGE=On \ -DCMAKE_C_COMPILE...

...fuzzers in the LLVM tree doesn't seem to >> work any more (possibly as of moving libFuzzer to compiler-rt, but there >> have been a few other changes in the last week or so that may be related). >> >> I'm building with a fresh top-of-tree clang and setting >> -DLLVM_USE_SANITIZER=Address and -DLLVM_USE_SANITIZE_COVERAGE=On, which >> was working before: >> >> % cmake -GNinja \ >> -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On \ >> -DLLVM_ENABLE_WERROR=On \ >> -DLLVM_USE_SANITIZER=Address -DLLVM_USE_...

...fuzzers in the LLVM tree doesn't seem to >> work any more (possibly as of moving libFuzzer to compiler-rt, but there >> have been a few other changes in the last week or so that may be related). >> >> I'm building with a fresh top-of-tree clang and setting >> -DLLVM_USE_SANITIZER=Address and -DLLVM_USE_SANITIZE_COVERAGE=On, which >> was working before: >> >> % cmake -GNinja \ >> -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On \ >> -DLLVM_ENABLE_WERROR=On \ >> -DLLVM_USE_SANITIZER=Address -DLLVM_USE_...

...in one of the bots, but I can't seem to get the right incantation of building LLVM with msan. Here's what I've been doing: 1) Build the toolchain in one build directory, including `compiler-rt`. 2) Build the toolchain again with the just built toolchain in step 1, but this time with `-DLLVM_USE_SANITIZER=MemoryWithOrigins`. I get some msan errors, but of this kind instead of the one I'm expecting: ==== $ ./unittests/XRay/XRayTests ==236769==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0x70eef8 (/usr/local/google/home/dberris/xray/llvm-project-build-msan/unittests/XRay/XRayT...

Hi lists, I am encountering a large number of check-clang failures after building Clang/LLVM with -DLLVM_USE_SANITIZER=Address. I have reported the issue on Bugzilla (https://bugs.llvm.org/show_bug.cgi?id=47678). I cannot even compile helloworld.c with the resulting clang tool without a lot of false positives from ASan. Is it because I am not supposed to use GCC's AddressSanitizer when building Clang? -- B...

...doesn't seem to > >> work any more (possibly as of moving libFuzzer to compiler-rt, but there > >> have been a few other changes in the last week or so that may be related). > >> > >> I'm building with a fresh top-of-tree clang and setting > >> -DLLVM_USE_SANITIZER=Address and -DLLVM_USE_SANITIZE_COVERAGE=On, which > >> was working before: > >> > >> % cmake -GNinja \ > >> -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On \ > >> -DLLVM_ENABLE_WERROR=On \ > >> -DLLVM_USE_...

...incantation of building LLVM with msan. > > Here's what I've been doing: > > > > 1) Build the toolchain in one build directory, including `compiler-rt`. > > > > 2) Build the toolchain again with the just built toolchain in step 1, > > but this time with `-DLLVM_USE_SANITIZER=MemoryWithOrigins`. > > > > I get some msan errors, but of this kind instead of the one I'm > expecting: > > > > ==== > > $ ./unittests/XRay/XRayTests > > ==236769==WARNING: MemorySanitizer: use-of-uninitialized-value > > #0 0x70eef8 > &gt...

...ith msan. > > > Here's what I've been doing: > > > > > > 1) Build the toolchain in one build directory, including `compiler-rt`. > > > > > > 2) Build the toolchain again with the just built toolchain in step 1, > > > but this time with `-DLLVM_USE_SANITIZER=MemoryWithOrigins`. > > > > > > I get some msan errors, but of this kind instead of the one I'm > expecting: > > > > > > ==== > > > $ ./unittests/XRay/XRayTests > > > ==236769==WARNING: MemorySanitizer: use-of-uninitialized-value >...

...rm for your own pass short of re-implementing loop-simplify yourself in your pass? I hope somebody here can and is willing to help me. Kind Regards Jean-Pierre Münch [1]: https://llvm.org/docs/CMake.html P.S.: While on my above "adventure" I noticed that building LLVM with clang and -DLLVM_USE_SANITIZER="MemoryWithOrigins" fails to complete because it apparently detects a bug in one of the build helper tools.

...erward will result in a SIGSEGV during stack unwinding. This suggests to me that somehow the stack is getting corrupted during the JITSymbol::getAddress() call. This problem was initially discovered while working on my own project. While troubleshooting this I've discvoered that when LLVM is -DLLVM_USE_SANITIZER:STRING=Address the problem happens at different points during execution, perhaps having something to do with the padding around the stack variables added by the sanitizer? See the note after the call to runTest() in main(). I'm running this under an up-to-date Antergos Linux, clang versio...

...ANITIZERS=on -DCOMPILER_RT_BUILD_XRAY=off \ -DLLVM_ENABLE_PROJECTS="clang;compiler-rt;lld;openmp" \ -DLLVM_ENABLE_ASSERTIONS=on -DLLVM_OPTIMIZED_TABLEGEN=on \ -DLLVM_STATIC_LINK_CXX_STDLIB=on -DLLVM_TARGETS_TO_BUILD="AArch64;X86" \ -DLLVM_USE_LINKER=gold -DLLVM_USE_SANITIZER=Address ../llvm Stage 1 was built from the same source using the same CMake command, without -DLLVM_USE_SANITIZER. CMAKE_C_FLAGS and CMAKE_CXX_FLAGS contained some hardening options like "-fstack-protector-strong -D_FORTIFY_SOURCE=2" which I omitted for brevity. I am building on an A...

...as of moving libFuzzer to compiler-rt, but >>> there >>> >> have been a few other changes in the last week or so that may be >>> related). >>> >> >>> >> I'm building with a fresh top-of-tree clang and setting >>> >> -DLLVM_USE_SANITIZER=Address and -DLLVM_USE_SANITIZE_COVERAGE=On, >>> which >>> >> was working before: >>> >> >>> >> % cmake -GNinja \ >>> >> -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On \ >>> >> -DLLVM_...

...unwinding. This suggests to me that somehow the stack is getting >> corrupted during the JITSymbol::getAddress() call. >> >> This problem was initially discovered while working on my own project. >> While troubleshooting this I've discvoered that when LLVM is >> -DLLVM_USE_SANITIZER:STRING=Address the problem happens at different >> points during execution, perhaps having something to do with the padding >> around the stack variables added by the sanitizer? See the note after the >> call to runTest() in main(). >> >> I'm running this unde...

...mehow the stack is getting >>>> corrupted during the JITSymbol::getAddress() call. >>>> >>>> This problem was initially discovered while working on my own project. >>>> While troubleshooting this I've discvoered that when LLVM is >>>> -DLLVM_USE_SANITIZER:STRING=Address the problem happens at different >>>> points during execution, perhaps having something to do with the padding >>>> around the stack variables added by the sanitizer? See the note after the >>>> call to runTest() in main(). >>>> &g...

Hi. Failure 1: Current clang-6.0 from http://apt.llvm.org/, current sources. $ CC=clang-6.0 CXX=clang++-6.0 cmake -DLLVM_ENABLE_PROJECTS="clang;libcxx;libcxxabi;compiler-rt;lld;polly;openmp" -DLLVM_USE_SANITIZER="Address;Undefined" -DCMAKE_BUILD_TYPE=Release -GNinja ../llvm $ ninja [200/3921] Building Attributes.gen... FAILED: include/llvm/IR/Attributes.gen.tmp cd /build/build-test && /build/build-test/bin/llvm-tblgen -gen-attrs -I /build/llvm/include/llvm/IR -I /build/llvm/include /b...

...gt;>> there >> >>> >> have been a few other changes in the last week or so that may be >> >>> related). >> >>> >> >> >>> >> I'm building with a fresh top-of-tree clang and setting >> >>> >> -DLLVM_USE_SANITIZER=Address and -DLLVM_USE_SANITIZE_COVERAGE=On, >> >>> which >> >>> >> was working before: >> >>> >> >> >>> >> % cmake -GNinja \ >> >>> >> -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTION...

...t;>> corrupted during the JITSymbol::getAddress() call. >>>>>> >>>>>> This problem was initially discovered while working on my own >>>>>> project. While troubleshooting this I've discvoered that when LLVM is >>>>>> -DLLVM_USE_SANITIZER:STRING=Address the problem happens at different >>>>>> points during execution, perhaps having something to do with the padding >>>>>> around the stack variables added by the sanitizer? See the note after the >>>>>> call to runTest() in mai...

I decided to try 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_s...

...gt;> >> have been a few other changes in the last week or so that may be >>>> >>> related). >>>> >>> >> >>>> >>> >> I'm building with a fresh top-of-tree clang and setting >>>> >>> >> -DLLVM_USE_SANITIZER=Address and -DLLVM_USE_SANITIZE_COVERAGE=O >>>> n, >>>> >>> which >>>> >>> >> was working before: >>>> >>> >> >>>> >>> >> % cmake -GNinja \ >>>> >>> >>...

...anges in the last week or so that may > be > >>>>> >>> related). > >>>>> >>> >> > >>>>> >>> >> I'm building with a fresh top-of-tree clang and setting > >>>>> >>> >> -DLLVM_USE_SANITIZER=Address and > -DLLVM_USE_SANITIZE_COVERAGE=O > >>>>> n, > >>>>> >>> which > >>>>> >>> >> was working before: > >>>>> >>> >> > >>>>> >>> >> % cmake...