public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: bkoz@gcc.gnu.org, bkoz@redhat.com, nathan@codesourcery.com,
	gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	sefer@hotmail.com
Subject: Re: libstdc++/8430: Found a memory leak in libstdc++-v3
Date: Tue, 07 Jan 2003 16:29:00 -0000	[thread overview]
Message-ID: <20030107162919.3544.qmail@sources.redhat.com> (raw)

Synopsis: Found a memory leak in libstdc++-v3

Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Tue Jan  7 08:29:17 2003
Responsible-Changed-Why:
    Mine.
State-Changed-From-To: open->closed
State-Changed-By: bkoz
State-Changed-When: Tue Jan  7 08:29:17 2003
State-Changed-Why:
    GLIBCPP_FORCE_NEW as put into 3.2.2 for this reason. With this release, you should get accurate results with current valgrind. 
    
    Please see this note for instructions and hints for using valgrind with g++/libstdc++:
    http://gcc.gnu.org/onlinedocs/libstdc++/debug.html

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8430


             reply	other threads:[~2003-01-07 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 16:29 bkoz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-02 10:06 B. Kosnik
2002-11-02  9:06 sefer

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=20030107162919.3544.qmail@sources.redhat.com \
    --to=bkoz@gcc.gnu.org \
    --cc=bkoz@redhat.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nathan@codesourcery.com \
    --cc=nobody@gcc.gnu.org \
    --cc=sefer@hotmail.com \
    /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: link
Be 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).