This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/6582: memory leaks in iostream and locale
- From: bkoz at gcc dot gnu dot org
- To: bkoz at gcc dot gnu dot org, gawrilow at math dot tu-berlin dot de, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
- Date: 15 May 2002 14:42:34 -0000
- Subject: Re: libstdc++/6582: memory leaks in iostream and locale
- Reply-to: bkoz at gcc dot gnu dot org, bkoz at gcc dot gnu dot org, gawrilow at math dot tu-berlin dot de, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: memory leaks in iostream and locale
Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Wed May 15 07:42:33 2002
Responsible-Changed-Why:
Mine.
State-Changed-From-To: open->feedback
State-Changed-By: bkoz
State-Changed-When: Wed May 15 07:42:33 2002
State-Changed-Why:
Please consider using the soon-to-be released 3.1.0, or mainline 3.2 sources. Both have revamped allocation strategies from the code you are using, and neither have the problems you are reporting. I've checked with valgrind and the current sources, and everything looks ok except for one issue with the underlying "C" locale information, which valgrind displays as a 16 and a 64 byte leak. These are to be expected.
Before the allocation tuning happened, there were 53 such issues.
-benjamin
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6582