public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Carlo Wood <carlo@alinoe.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/10276: memory leak for stringstream / ios_base callback cache.
Date: Mon, 31 Mar 2003 23:16:00 -0000 [thread overview]
Message-ID: <20030331231601.19583.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/10276; it has been noted by GNATS.
From: Carlo Wood <carlo@alinoe.com>
To: ehrhardt@mathematik.uni-ulm.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: libstdc++/10276: memory leak for stringstream / ios_base callback cache.
Date: Tue, 1 Apr 2003 01:13:20 +0200
Just got another mail.
Benjamin Kosnik confirmed it again, apparently it should
be assigned to Jerry, not Loren.
See http://gcc.gnu.org/ml/libstdc++/2003-03/msg00383.html
--
Carlo Wood <carlo@alinoe.com>
next reply other threads:[~2003-03-31 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 23:16 Carlo Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-29 16:06 bkoz
2003-04-01 9:49 ehrhardt
2003-03-31 23:16 Carlo Wood
2003-03-31 17:40 ehrhardt
2003-03-31 13:36 carlo
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=20030331231601.19583.qmail@sources.redhat.com \
--to=carlo@alinoe.com \
--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).