Hi Alexey, thank you very much! Running my program with
*export LSAN_OPTIONS=suppressions=./supressions.txt;print_suppressions=0* does exactly what I wanted. - Konrad Am Freitag, 22. Mai 2015 20:40:33 UTC+2 schrieb Alexey Samsonov: > > Hi Konrad, > > Blacklist doesn't work for disabling memory leaks. I think you should try > suppressions instead ( > https://code.google.com/p/address-sanitizer/wiki/LeakSanitizer). You can > add the following line to suppressions.txt "leak:*mylib.so", and then run > your program with LSAN_OPTIONS=suppressions=/path/to/suppressions.txt env > var. > > On Fri, May 22, 2015 at 7:58 AM, Konrad Wilhelm <[email protected] > <javascript:>> wrote: > >> Hi, >> >> I'm facing an issue with a dynamically loaded third-party library. >> >> To better illustrate the problem, I've create this self-contained C >> project on github: https://github.com/kwk/asan-dlopen-issue >> >> The library contains a memory leak that is correctly found when I compile >> my program with address sanitizer. But now I want to blacklist it to be >> ignore and no longer clutter my ASAN log output. >> >> This doesn't work (see github project for description)! >> >> Any solution on how to blacklist either the caller or the callee would be >> helpful. >> >> Thanks in advance >> - Konrad >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Alexey Samsonov, Mountain View, CA > -- 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.
