This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/4164: 33 Memory Leak when using iostream
- From: pme at gcc dot gnu dot org
- To: allali at univ-mlv dot fr, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
- Date: 19 Apr 2002 20:04:12 -0000
- Subject: Re: libstdc++/4164: 33 Memory Leak when using iostream
- Reply-to: pme at gcc dot gnu dot org, allali at univ-mlv dot fr, 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: 33 Memory Leak when using iostream
State-Changed-From-To: open->feedback
State-Changed-By: pme
State-Changed-When: Fri Apr 19 13:04:10 2002
State-Changed-Why:
Backtraces from a tool we don't have do not help us, especially when the backtraces do not specify /where/ the suspected memory leak takes place. Can you specify function names or line numbers?
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4164