libstdc++/7843: Memory not freed when printing complex number

[Jeffrey Oldham]

bkoz@gcc.gnu.org wrote:
> Synopsis: Memory not freed when printing complex number
> 
> Responsible-Changed-From-To: unassigned->bkoz
> Responsible-Changed-By: bkoz
> Responsible-Changed-When: Tue Nov  5 19:30:14 2002
> Responsible-Changed-Why:
>     Mine.
> State-Changed-From-To: open->feedback
> State-Changed-By: bkoz
> State-Changed-When: Tue Nov  5 19:30:14 2002
> State-Changed-Why:
>     Hey. I think this was fixed a while back. I'm using valgrind on RH8, and I don't see anything with this output. Note, the pool allocators used by default with libstdc++ may confuse memory checking programs. There's a way around this for CVS head, where you can switch to the malloc_alloc allocators with GLIBCPP_USE_NEW defined. That work will work its way into gcc-3_2-branch for the next stable release.
>     
>     best,
>     benjamin
> 
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7843

Thanks for looking into this.

Jeffrey D. Oldham
oldham@codesourcery.com