libstdc++/6246: gcc generates code that memleaks

[Clemens Kirchgatterer]

The following reply was made to PR libstdc++/6246; it has been noted by GNATS.

From: Clemens Kirchgatterer <clemens@thf.ath.cx>
To: rodrigc@gcc.gnu.org, clemens@thf.ath.cx, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/6246: gcc generates code that memleaks
Date: Sat, 13 Apr 2002 08:29:34 +0200

 rodrigc@gcc.gnu.org wrote:
 
 > Synopsis: gcc generates code that memleaks
 > 
 > State-Changed-From-To: open->closed
 > State-Changed-By: rodrigc
 > State-Changed-When: Fri Apr 12 19:02:25 2002
 > State-Changed-Why:
 >     Cannot duplicate with gcc 3.0.4
 
 hi!
 
 hmm, this is very strange, as it is NOT gcc's fault, but mine.
 
 *buf += str.str(); <--  this freazes the buffer and returns a
                         pointer to it. the caller is now
                         responsible for freeing it with delete().
 
 so, the testprogramm MUST memleak as it is, independently from
 the compiler. can you have a look at it, to make this clear?
 
 thanx & sorry for bothering you!
 
 clemens