You are welcome!
On Wed, Jul 23, 2014 at 11:46 AM, Jonathan <[email protected]> wrote: > > > Le mardi 22 juillet 2014 23:15:07 UTC+2, Jonathan a écrit : >> >> >> >> Le mardi 22 juillet 2014 21:25:05 UTC+2, Dmitry Vyukov a écrit : >>> >>> 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. >> >> >> >> Will try that but the project is compiled with -O1. Also with an older >> clang+asan I know there is a problem in a third library that isn't reported >> with version. (about overlap memory with memcpy() ) > > > After retrying with printf() it works as expected, so the code was optimized > away as you said, sorry for the trouble. > Thanks for the help. > > -- > 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. -- 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.
