public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "B. Kosnik" <bkoz@nabi.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/8430: Found a memory leak in libstdc++-v3 Date: Sat, 02 Nov 2002 10:06:00 -0000 [thread overview] Message-ID: <20021102180600.13022.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/8430; it has been noted by GNATS. From: "B. Kosnik" <bkoz@nabi.net> To: sefer@hotmail.com Cc: gcc-gnats@gcc.gnu.org, bkoz@redhat.com, nathan@codesourcery.com Subject: Re: libstdc++/8430: Found a memory leak in libstdc++-v3 Date: Sat, 2 Nov 2002 12:00:30 -0600 Don't use the default allocators. GLIBCPP_FORCE_NEW http://gcc.gnu.org/onlinedocs/libstdc++/ext/howto.html#6
next reply other threads:[~2002-11-02 18:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-02 10:06 B. Kosnik [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-07 16:29 bkoz 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=20021102180600.13022.qmail@sources.redhat.com \ --to=bkoz@nabi.net \ --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: linkBe 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).