Re: [cfe-users] How to enable Initialization Order Fiasco sanitizer from the command line?

2016-01-11 Thread Alexey Samsonov via cfe-users
To quote Reid's response from another group: """ If you want to bake in some options at compile time, there are a few ways to do it. -DASAN_DEFAULT_OPTIONS=check_initialization_order=true will work, or you can define the __asan_default_options function somewhere in the binary like this: extern "C

Re: [cfe-users] Clang memory sanitizer: llvm-symbolizer problem

2015-11-25 Thread Alexey Samsonov via cfe-users
On Wed, Nov 25, 2015 at 4:12 AM, Schlottke-Lakemper, Michael < m.schlottke-lakem...@aia.rwth-aachen.de> wrote: > > Thus I tried to compile a complete LLVM/Clang stack (with compiler-rt, >> libcxx, libcxxabi, libomp) using -DLLVM_USE_SANITIZER=MemoryWithOrigins. >> However, this did not work either

Re: [cfe-users] Clang memory sanitizer: llvm-symbolizer problem

2015-11-24 Thread Alexey Samsonov via cfe-users
On Tue, Nov 24, 2015 at 9:12 AM, Schlottke-Lakemper, Michael via cfe-users < cfe-users@lists.llvm.org> wrote: > Short update: I thought the behavior reported below it might be related to > the fact that llvm-symbolizer picks up the “wrong” (i.e. the > msan-implemented) version of libc++ once I put

Re: [cfe-users] Problem with address sanitizer stack traces

2015-11-24 Thread Alexey Samsonov via cfe-users
Try to add ASAN_OPTIONS=fast_unwind_on_malloc=0. It's possible that stack traces go through smth. like libstdc++ which is built without frame pointers. On Tue, Nov 24, 2015 at 12:49 AM, Rainer Gerhards via cfe-users < cfe-users@lists.llvm.org> wrote: > Hi all, > > first, thanks for the great tool