public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/2517
Date: Wed, 02 May 2001 11:16:00 -0000	[thread overview]
Message-ID: <20010502181601.11694.qmail@sourceware.cygnus.com> (raw)

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

From: bkoz@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, knuteson@fnal.gov, nobody@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/2517
Date: 2 May 2001 18:07:13 -0000

 Synopsis: -O2 compilation appears to cause a memory leak when a string is added to a char[]
 
 State-Changed-From-To: open->analyzed
 State-Changed-By: bkoz
 State-Changed-When: Wed May  2 11:07:12 2001
 State-Changed-Why:
     This is a bug, reproduced with current sources. I've pingged nathan but no response...
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2517&database=gcc


             reply	other threads:[~2001-05-02 11:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 11:16 bkoz [this message]
2001-05-24 18:56 libstdc++/2517 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=20010502181601.11694.qmail@sourceware.cygnus.com \
    --to=bkoz@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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: 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).