Hi Lukas, Please try running docker with "--cap-add SYS_PTRACE". LeakSanitizer uses ptrace and by default ptrace is disabled in docker. If this doesn't help, please provide more details.
--kcc On Thu, Aug 9, 2018 at 12:44 AM Lukas Woodtli <[email protected]> wrote: > Hi there > > We have some C++ testing applications that we run with a sanatizer (asan) > enabled build. > Now we decided to run these application in a Docker container. In the > container > asan reports some leaks that are not reported when run natively. > At a first glance the reported issues seem to be false positives mainly > occuring > in static (or thread local) data. > > The OS is RHEL7 (also inside of Docker) > > Any hints why the allocator behaves differently in these environments. > > Regards, > Lukas > > -- > 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.
