public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nanjiang dot shu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/27615] memory leak with libstdc++ set <string>
Date: Mon, 15 May 2006 15:50:00 -0000 [thread overview]
Message-ID: <20060515155045.19012.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27615-12688@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from nanjiang dot shu at gmail dot com 2006-05-15 15:50 -------
Subject: Re: memory leak with libstdc++ set <string>
I have compiled the problem with gcc4.1.0, which was builded under
linux-pc-i686 from tar balls. The program exited with similar error
message. But I did not debuged with libcwd then. Unforturnately, the
computer with gcc4.1.0 installed is down right now.
I guess the bug is still exist in gcc 4.1.0
/Nanjiang
On 15 May 2006 15:35:40 -0000, pinskia at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #1 from pinskia at gcc dot gnu dot org 2006-05-15 15:35 -------
> Can you try a newer GCC since 3.3.x (and 3.4.x) are no longer being updated.
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27615
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27615
next prev parent reply other threads:[~2006-05-15 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 15:28 [Bug libstdc++/27615] New: " nanjiang dot shu at gmail dot com
2006-05-15 15:35 ` [Bug libstdc++/27615] " pinskia at gcc dot gnu dot org
2006-05-15 15:50 ` nanjiang dot shu at gmail dot com [this message]
2006-05-15 16:47 ` pcarlini at suse dot de
2006-08-15 18:23 ` pinskia at gcc dot gnu dot org
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=20060515155045.19012.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).