search for: asan_interfac

Hi, I would like to improve the debugging experience for ASan. The idea is to have a couple of useful commands in LLDB (probably implemented as Python scripts) that could help the user when they are debugging an ASan-enabled binary. We already have some debugging API (asan_interface.h): // Print the description of addr (useful when debugging in gdb). void __asan_describe_address(void *addr); What I'd like to have is a few more API on the ASan/compiler-rt side to query various information that ASan can provide, both about an error report and about general address...

...OID=1 \ -DCMAKE_SYSTEM_NAME=Linux \ -DCMAKE_C_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm \ -DCMAKE_CXX_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm ... $ ninja install ... [68/68] -- Install configuration: "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 -- Insta...

> On Sep 6, 2017, at 9:14 PM, Kostya Serebryany <kcc at google.com> wrote: > > > > On Wed, Sep 6, 2017 at 8:43 AM, Jonas Devlieghere via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > Hi all, > > Is it possible to change the value of ASan's allocator_may_return_null at runtime or somehow disable this check

> This is a public interface. But ASan runtime (and test-suite) strongly depends on > the instrumentation pass in Clang. How do you feel about adding a runtime init check of a version number defined by asan_interface.h? -Greg On Tue, Apr 22, 2014 at 11:16 AM, Alexey Samsonov <samsonov at google.com> wrote: > > On Tue, Apr 22, 2014 at 10:43 AM, Greg Fitzgerald <garious at gmail.com> wrote: >> >> Sorry for the slow replies. I'm out on vacation this week. >> >> &g...

...ysroot=$(ndkDir)/platforms/android-19/arch-arm \ >> -DCMAKE_CXX_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm >> ... >> $ ninja install >> ... >> [68/68] >> -- Install configuration: "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: shi...

...;>> -DCMAKE_CXX_FLAGS=--sysroot=$(ndkDir)/platforms/android-19/arch-arm >>>> ... >>>> $ ninja install >>>> ... >>>> [68/68] >>>> -- Install configuration: "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_interfa...

...atforms/android-19/arch-arm >> >>>> ... >> >>>> $ ninja install >> >>>> ... >> >>>> [68/68] >> >>>> -- Install configuration: "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:...

...>> ... > >>> >>>> $ ninja install > >>> >>>> ... > >>> >>>> [68/68] > >>> >>>> -- Install configuration: "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 > >>...

...t makes more sense to > namespace every variable. We can avoid painting that bike shed using > CMAKE_PREFIX_PATH. > > When one component has multiple dependencies from another, using > CMAKE_PREFIX_PATH really starts saving keystrokes. You can use it to > find headers (sanitizer/asan_interface.h), binaries (FileCheck), > libraries, or CMake modules. > > A good alternative to CMAKE_PREFIX_PATH is to create one variable per > install directory. So compiler-rt might accept LLVM_INSTALL_DIR, and > clang accept COMPILER_RT_INSTALL_DIR and LLVM_INSTALL_DIR. There are > two...

On Thu, Mar 20, 2014 at 10:12 PM, Greg Fitzgerald <garious at gmail.com> wrote: > > ExternalProject_Add(compiler-rt ...) > > So that was quite the experiment. Looking at > clang/runtime/CMakeLists.txt, I'm not seeing a lot of bang for buck > here, and it looks like this file is prone to bit rot. Could you please elaborate on this? In fact, I don't plan to give

Sorry for the slow replies. I'm out on vacation this week. Alexey wrote: > If you want to test the sanitizer runtiume library "during development", > you should verify that it works with the Clang at hand. I want to test an implementation of libraries, not that clang links a library in its install directory. We only need one clang test for the latter (not 100) and that

...gt;>> $ ninja install > >> >>> >>>> ... > >> >>> >>>> [68/68] > >> >>> >>>> -- Install configuration: "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_sy...