public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pme@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, pme@gcc.gnu.org, stevemw@place.org Subject: Re: libstdc++/1853: <deque> deallocates unowned memory within .pop_back() Date: Fri, 28 Dec 2001 15:51:00 -0000 [thread overview] Message-ID: <20011228235111.9253.qmail@sources.redhat.com> (raw) Synopsis: <deque> deallocates unowned memory within .pop_back() Responsible-Changed-From-To: unassigned->pme Responsible-Changed-By: pme Responsible-Changed-When: Fri Dec 28 15:51:10 2001 Responsible-Changed-Why: I changed it. Still an issue as of today. The internals of deque aren't documented very well at all. I want to figure out what memory games are being played before changing the code; the obvious solution may be too slow. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=1853
next reply other threads:[~2001-12-28 23:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-28 15:51 pme [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-02 21:00 pme 2001-06-12 14:14 bkoz 2001-04-01 0:00 stevemw
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=20011228235111.9253.qmail@sources.redhat.com \ --to=pme@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=stevemw@place.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).