search for: lsan_interfac

On Thu, Dec 26, 2013 at 2:40 AM, Kostya Serebryany <kcc at google.com> wrote: > Like this? > > +extern "C" { > +// Disable LeakSanitizer, see http://llvm.org/bugs/show_bug.cgi?id=18325. > We don't often reference bugs in comments. I would give a brief summary in the text of the comment, and mention the bug in the commit log. -------------- next part

...t of the comment, and mention the bug in the commit log. > This? > > +extern "C" { > +// Disable LeakSanitizer for this binary as it has too many leaks that are not > +// very interesting to fix. __lsan_is_turned_off is explained in > +// compiler-rt/include/sanitizer/lsan_interface.h > +int __lsan_is_turned_off() { return 1; } > +} // extern “C" [ Sorry to be joining the conversation late ] What is the reasoning behind having them define a function to disable lsan, rather than calling __lsan_disable? Is it so that lsan can be turned off before main() is entered...

...uration: "Release" -- Installing: ship/include/sanitizer/asan_interface.h -- Installing: ship/include/sanitizer/common_interface_defs.h -- Installing: ship/include/sanitizer/dfsan_interface.h -- Installing: ship/include/sanitizer/linux_syscall_hooks.h -- Installing: ship/include/sanitizer/lsan_interface.h -- Installing: ship/include/sanitizer/msan_interface.h -- Installing: ship/include/sanitizer/tsan_interface_atomic.h -- Installing: ship/asan_blacklist.txt -- Installing: ship/bin/asan_device_setup Thanks, Greg

...alling: ship/include/sanitizer/asan_interface.h >> -- Installing: ship/include/sanitizer/common_interface_defs.h >> -- Installing: ship/include/sanitizer/dfsan_interface.h >> -- Installing: ship/include/sanitizer/linux_syscall_hooks.h >> -- Installing: ship/include/sanitizer/lsan_interface.h >> -- Installing: ship/include/sanitizer/msan_interface.h >> -- Installing: ship/include/sanitizer/tsan_interface_atomic.h >> -- Installing: ship/asan_blacklist.txt >> -- Installing: ship/bin/asan_device_setup >> >> Thanks, >> Greg

...san_interface.h >>>> -- Installing: ship/include/sanitizer/common_interface_defs.h >>>> -- Installing: ship/include/sanitizer/dfsan_interface.h >>>> -- Installing: ship/include/sanitizer/linux_syscall_hooks.h >>>> -- Installing: ship/include/sanitizer/lsan_interface.h >>>> -- Installing: ship/include/sanitizer/msan_interface.h >>>> -- Installing: ship/include/sanitizer/tsan_interface_atomic.h >>>> -- Installing: ship/asan_blacklist.txt >>>> -- Installing: ship/bin/asan_device_setup >>>> >>>&...

Hi, I'm currently trying to find and fix memory leaks (compiling with ``-fsanitize=address``) in the KLEE tool [1] an having found some leaks and I'm having trouble suppressing them. I'm trying to suppress them using the ``-fsanitize-blacklist=blacklist.txt`` option as documented at [2]. I'm using Clang 3.7 ( Arch Linux package 3.7.0-6). The sort of reported leaks I see are ```

...;> -- Installing: ship/include/sanitizer/common_interface_defs.h >> >>>> -- Installing: ship/include/sanitizer/dfsan_interface.h >> >>>> -- Installing: ship/include/sanitizer/linux_syscall_hooks.h >> >>>> -- Installing: ship/include/sanitizer/lsan_interface.h >> >>>> -- Installing: ship/include/sanitizer/msan_interface.h >> >>>> -- Installing: ship/include/sanitizer/tsan_interface_atomic.h >> >>>> -- Installing: ship/asan_blacklist.txt >> >>>> -- Installing: ship/bin/asan_device_...

...nclude/sanitizer/common_interface_defs.h > >>> >>>> -- Installing: ship/include/sanitizer/dfsan_interface.h > >>> >>>> -- Installing: ship/include/sanitizer/linux_syscall_hooks.h > >>> >>>> -- Installing: ship/include/sanitizer/lsan_interface.h > >>> >>>> -- Installing: ship/include/sanitizer/msan_interface.h > >>> >>>> -- Installing: ship/include/sanitizer/tsan_interface_atomic.h > >>> >>>> -- Installing: ship/asan_blacklist.txt > >>> >>>>...

Hi All, Currently libfuzzer depends on (often freshly built) clang, yet the dependency is not explicitly specified in cmake. That leads to various issues: for instance, it’s not possible to check out LLVM repo and run libfuzzer tests: one would often need to compile fresh clang first, and then create a separate build directory, where libfuzzer could be tested. For the buildbot this problem is

...erface_defs.h > >> >>> >>>> -- Installing: ship/include/sanitizer/dfsan_interface.h > >> >>> >>>> -- Installing: ship/include/sanitizer/linux_syscall_hooks.h > >> >>> >>>> -- Installing: ship/include/sanitizer/lsan_interface.h > >> >>> >>>> -- Installing: ship/include/sanitizer/msan_interface.h > >> >>> >>>> -- Installing: ship/include/sanitizer/tsan_interface_atomic.h > >> >>> >>>> -- Installing: ship/asan_blacklist.txt > &gt...

...64 i386 i686) if(ANDROID) set(OS_NAME "Android") diff --git a/include/CMakeLists.txt b/include/CMakeLists.txt index 7f8664e..7c34aee 100644 --- a/include/CMakeLists.txt +++ b/include/CMakeLists.txt @@ -6,7 +6,8 @@ set(SANITIZER_HEADERS sanitizer/linux_syscall_hooks.h sanitizer/lsan_interface.h sanitizer/msan_interface.h - sanitizer/tsan_interface_atomic.h) + sanitizer/tsan_interface_atomic.h + safestack_interface.h) set(output_dir ${COMPILER_RT_OUTPUT_DIR}/include) diff --git a/include/safestack_interface.h b/include/safestack_interface.h new file mode 100644 index 0000000....