search for: ubsan

> On Jul 21, 2017, at 6:04 AM, Shi, Steven via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >>> I think your best bet for controlling code bloat is to compile with >>> -fsanitize=undefined -fsanitize-trap=undefined. >> >> Also you may not need all of UBSan's checks at the same time -- so pick >> and choose among its checks using the finer-grained flags. >> >> If you're really stuck against a hard limit on code size, try applying >> UBSan to a subset of files in your project at a time. > > Hi John, > Thank yo...

Hi all, TL;DR 1) We should change the way we parse common runtime flags in sanitizers. 2) We should make ASan aware of the tools it can be combined with (LSan and UBSan). 3) We may have to restrict the tools UBSan can be combined with (currently to ASan) (see [1]) Currently we have two kinds of sanitizer runtime flags: tool-specific flags and "common flags", defined in sanitizer_common library and shared across all the sanitizers. Many of these common f...

Hi, I've just tagged LLVM 9.0.1-rc3. Testers can begin testing and uploading binaries. This will be the last release candidate unless there is a major problem. I'm planning to tag the final release on Dec 19. -Tom

I've been working on adding UBSan support to CMake (so that errors found by it can be uploaded to CDash for viewing). One problem is that the message is very generic. The patch here addes 'UndefinedBehaviorSanitizer' to the message so that they may be detected more easily. If something else is wanted (such as the '===&...

CRAN has a package of mine in upload limbo because it failed UBSAN. I am not entirely ignorant on the topic of sanitizers and SAN / ASAN / UBSAN; we created not one but two Docker containers with ASAN and USBAN: https://registry.hub.docker.com/u/rocker/r-devel-san/ https://registry.hub.docker.com/u/rocker/r-devel-ubsan-clang/ as well as predecessors to th...

Hello, I'm investigating on enabling the Ubsan in my firmware. I have two questions about Ubsan: 1. I see the Ubsan run-time lib functions are defined in http://llvm.org/svn/llvm-project/compiler-rt/trunk/lib/ubsan/ubsan_interface.inc, but I cannot find how the LLVM implement the Ubsan instrumentations. I see the Asan's instrumen...

Hi, I've tagged the LLVM 9.0.1-rc1 release. Testers can begin testing and upload binaries. I've also updated the test-release.sh script to pull from GitHub instead of SVN, if you run into any issues with the new script, let me know. -Tom

Hi, I've just tagged the 9.0.1-final release. Testers can begin uploading binaries. -Tom

On Mon, Dec 8, 2014 at 2:00 AM, Alexander Potapenko <glider at google.com> wrote: > Hope you're assuming there's always a single copy of common_flags in > the process. > This isn't the case for e.g. ASan+UBSan on Mac, but that's a broken setup. > > What if we let the tools protect specific flags (by adding a bool to > each flag) once they set their values (when setting the default > values, parsing xSAN_OPTIONS, etc) > Generally, I think we need to protect each flag when anyone's t...

Hello, I have several low priority UBSan questions... (1) Is there a way for UBSan to print its output to a file that the user specified (e.g. via option) instead of dumping everything on stderr? (2) Out of curiosity, why is the name of the option for printing the stacktrace spelled "UBSAN_OPTIONS=print_stacktrace=1", thoug...

Hi, I've tagged LLVM 9.0.1-rc2. Testers can begin testing and uploading binaries. If all goes well, this will be the last -rc. -Tom

...ib64/libxml2.so (found version "2.7.8") -- Found Subversion: /usr/bin/svn (found version "1.6.17") -- Configuring done -- Generating done -- Build files have been written to: /current/dir ========= Build Error: ========= [161/2079] Building CXX object projects/compiler-rt/lib/ubsan/CMakeFiles/clang_rt.ubsan-i386.dir/ubsan_value.cc.o FAILED: /usr/bin/c++ -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fPIC -fvisibility-inlines-hidden -g -Iprojects/compiler-rt/lib/ubsan -I/local/home/mahesha/src/12th_Sep/llvm/projects/compiler-rt/...

Hi Adhemerval, Some UBSan tests are timing out randomly. http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full ex: http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full/builds/902 http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full/builds/894 http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full/buil...

I'm seeing this too. CC'ing the author ubsan stuff. Richard, I know you were OK with only supporting Clang-bootstraps, but I don't think that's terribly viable here. We should be able to build ubsan's runtime with standards conforming code unless there is some fairly extreme reason not to... On Fri, Oct 12, 2012 at 7:19 AM, Mah...

Hello all! (+cc Vedant Kumar, who I've been told knows a lot about UBSan!) I am trying to fix an assert that occurs when the transforms in llvm/lib/Transforms/Coroutines are applied to LLVM IR that has been generated with UBSan enabled -- specifically, '-fsanitize=null'. You can see an example of the assert in this 26-line C++ file here: https://godbolt.org/g/...

...Found Subversion: /usr/bin/svn (found version "1.6.17") > -- Configuring done > -- Generating done > -- Build files have been written to: /current/dir > > > ========= > Build Error: > ========= > > [161/2079] Building CXX object > projects/compiler-rt/lib/ubsan/CMakeFiles/clang_rt.ubsan-i386.dir/ubsan_value.cc.o > FAILED: /usr/bin/c++ -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS > -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fPIC > -fvisibility-inlines-hidden -g -Iprojects/compiler-rt/lib/ubsan > -I/local/home/mahesha/src/12th_Sep/llvm/p...

On Fri, Oct 12, 2012 at 6:14 PM, Chandler Carruth <chandlerc at google.com> wrote: > I'm seeing this too. CC'ing the author ubsan stuff. > > Richard, I know you were OK with only supporting Clang-bootstraps, but I > don't think that's terribly viable here. Just out of curiosity - why isn't that viable? I'd sort of hope to treat optional sanitizer runtimes like, say, lld or other projects that aren...

Hi, I have just tagged 3.7.1-rc1, so it is ready for testing. As a reminder, when doing regression testing, use the 3.7.0 release as your baseline. Thanks, Tom

...BUILD=host \ -DLLVM_TARGET_ARCH=host \ -DLLVM_LIBDIR_SUFFIX=64 \ -DCLANG_DEFAULT_CXX_STDLIB=libc++ \ -DLLVM_ENABLE_LIBCXX=ON .. results in the following build error: ../projects/compiler-rt/lib/ubsan/ubsan_type_hash_itanium.cc:233: error: undefined reference to 'typeinfo for std::type_info' ../projects/compiler-rt/lib/ubsan/ubsan_type_hash_itanium.cc:233: error: undefined reference to 'typeinfo for __cxxabiv1::__class_type_info' ../projects/compiler-rt/lib/ubsan/ubsan_type_hash...

> On Mar 19, 2018, at 3:44 PM, Brian Gesiak <modocache at gmail.com> wrote: > > Hello all! > (+cc Vedant Kumar, who I've been told knows a lot about UBSan!) > > I am trying to fix an assert that occurs when the transforms in llvm/lib/Transforms/Coroutines are applied to LLVM IR that has been generated with UBSan enabled -- specifically, '-fsanitize=null'. > > You can see an example of the assert in this 26-line C++ file here: ht...