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

[Dan K. <da...@ke...>]

On Sat, Mar 4, 2017 at 9:46 AM, Ulrich Hierl <kni...@fr...> 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<char> const&)
> by : char* std::string::_S_construct<char const*>(char const*, char const*, std::allocator<char> const&, std::forward_iterator_tag)
> by : testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, testing::internal::CodeLocation, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*) (gtest.cc:2555)
> by : __static_initialization_and_destruction_0(int, int) (ClassFilesManipulator_expensive_tests.cpp:166)

That looks like an expected and benign leak from google test.
I'd just suppress it, and anything else from testing::internal.
- Dan