Bug#231233: libstdc++5: std::map memory is not freed

[Jeremy Nimmer <jwnimmer@alum.mit.edu>]

On Thu, 2004-02-05 at 04:25, Daniel Kraft wrote:
> ... having a way to make libstdc++ free [its memory pool]
> would make finding real leaks easier.

See the valgrind FAQ, question #14:
http://valgrind.kde.org/faq.html

Quoting...

        Using gcc, you can force the STL to use malloc and to free
        memory as soon as possible by globally disabling memory
        caching.  Beware!  Doing so will probably slow down your
        program, sometimes drastically.
         
        With 3.2.2 and later, you should export the environment 
        variable GLIBCPP_FORCE_NEW before running your program.

It is also spelled GLIBCXX_FORCE_NEW in later GCC versions.  Something
like that should work for you.

Thanks,
- Jeremy