This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/8430: Found a memory leak in libstdc++-v3
- From: bkoz at gcc dot gnu dot org
- To: bkoz at gcc dot gnu dot org, bkoz at redhat dot com, nathan at codesourcery dot com, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, sefer at hotmail dot com
- Date: 7 Jan 2003 16:29:19 -0000
- Subject: Re: libstdc++/8430: Found a memory leak in libstdc++-v3
- Reply-to: bkoz at gcc dot gnu dot org, bkoz at gcc dot gnu dot org, bkoz at redhat dot com, nathan at codesourcery dot com, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, sefer at hotmail dot com, gcc-gnats at gcc dot gnu dot org
Synopsis: Found a memory leak in libstdc++-v3
Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Tue Jan 7 08:29:17 2003
Responsible-Changed-Why:
Mine.
State-Changed-From-To: open->closed
State-Changed-By: bkoz
State-Changed-When: Tue Jan 7 08:29:17 2003
State-Changed-Why:
GLIBCPP_FORCE_NEW as put into 3.2.2 for this reason. With this release, you should get accurate results with current valgrind.
Please see this note for instructions and hints for using valgrind with g++/libstdc++:
http://gcc.gnu.org/onlinedocs/libstdc++/debug.html
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8430