C++'s std::string pools, debug builds? std::string and valgrind problems

Question

I have a problem with many valgrind warnings about possible memory leaks in std::string, like this one:

120 bytes in 4 blocks are possibly lost in loss recor         


        

Answer 1

I had this issue because my program terminated due to an uncaught exception. Apparently the handler for uncaught exceptions does not clean everything up.