On Tue, Jul 22, 2014 at 11:10 PM, Jonathan <[email protected]> wrote: > Hello, > > I'm currently experiencing something strange and I can't explain it. > I've compliled a ToT (approx. of today) LLMV/Clang/compiler-rt using libcxx > & libcxxabi on Linux (Debian 6.0) the shipped compiler is GCC 4.4 (so no > C++11 support). All compilations are done in 32-bit. > > When I run the target check-asan and all I only get 2 failed test (something > about the size of ThreadSize being bigger) so I assume the compiler & asan > are in a working state. > > So I made a litte test (simple main with char[] on the stack and strcpy() a > bigger array in it) as expected I get an Asan report. > > But if I copy the same code in my bigger project, there is no report from > Asan but I do get in another tool of the project report about ODR > violations. > If I set verbosity in ASAN_OPTIONS it loads correctly and I get a few > warning that the lib is not being able to intercept __c99_printf and a few > other functions that are basicaly related to printf. > > If I use "nm" on one of my binary I can see the __asan_init & other asan > functions. > > So is there a way to check if the code is instrumented for asan ? What could > be the problem here ? > > Thanks in advance for your help, >
It's possible that your buggy code is so simple that compiler optimizes it away. E.g. if your projects is compiled with -O2, but your test is -O0. Try to add some volatiles and prints. -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
