Re: [Valgrind-users] New leaks when running valgrind in a docker container

On Sat, Mar 4, 2017 at 9:46 AM, Ulrich Hierl wrote: > 101 bytes in 1 blocks are possibly lost in loss record 241 of 365 > at : operator new(unsigned long) > by : std::string::_Rep::_S_create(unsigned long, unsigned long, > std::allocator const&) > by : char*

[Valgrind-users] New leaks when running valgrind in a docker container

Hi valgrind folk, I am currently transforming my build-slave from a virtual machine to a docker container. One step of my build is to run valgrind. The problem is that I now get new memory leaks that do not occur on the virtual machine. The errors come from libc and std::string, here is an