libstdc++/6246: gcc generates code that memleaks

[Clemens Kirchgatterer]

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