public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jeffrey Oldham <oldham@codesourcery.com> To: bkoz@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/7843: Memory not freed when printing complex number Date: Tue, 05 Nov 2002 19:46:00 -0000 [thread overview] Message-ID: <20021106034602.8669.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/7843; it has been noted by GNATS. From: Jeffrey Oldham <oldham@codesourcery.com> To: bkoz@gcc.gnu.org, bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, oldham@codesourcery.com, gcc-gnats@gcc.gnu.org Cc: Subject: Re: libstdc++/7843: Memory not freed when printing complex number Date: Tue, 05 Nov 2002 19:40:30 -0800 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
next reply other threads:[~2002-11-06 3:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-05 19:46 Jeffrey Oldham [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-06 8:59 bkoz 2002-11-05 19:30 bkoz
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021106034602.8669.qmail@sources.redhat.com \ --to=oldham@codesourcery.com \ --cc=bkoz@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).