public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Clemens Kirchgatterer <clemens@thf.ath.cx>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/6246: gcc generates code that memleaks
Date: Fri, 12 Apr 2002 23:36:00 -0000	[thread overview]
Message-ID: <20020413063601.26343.qmail@sources.redhat.com> (raw)

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

From: Clemens Kirchgatterer <clemens@thf.ath.cx>
To: rodrigc@gcc.gnu.org, clemens@thf.ath.cx, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/6246: gcc generates code that memleaks
Date: Sat, 13 Apr 2002 08:29:34 +0200

 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


             reply	other threads:[~2002-04-13  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12 23:36 Clemens Kirchgatterer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-14 18:56 Carlo Wood
2002-04-12 19:02 rodrigc

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=20020413063601.26343.qmail@sources.redhat.com \
    --to=clemens@thf.ath.cx \
    --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).