public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chris at bubblescope dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/17012] std::list's function, remove, looks like it is reading memory that has been freed. Date: Tue, 05 Jul 2005 12:11:00 -0000 [thread overview] Message-ID: <20050705121111.25348.qmail@sourceware.org> (raw) In-Reply-To: <20040812195652.17012.debrak@sgi.com> ------- Additional Comments From chris at bubblescope dot net 2005-07-05 12:11 ------- It seems to me that this is just a simple NAB. There seems to be 3 options 1) Just leave it as is 2) Alter list::remove so in debug mode it aborts if you give it an element from the list 3) Alter list::remove so this code works (which in some very quick checking seems to produce about a ~15% slowdown on things like list<int>s) The similar problem on things in <algorithm> I think is more cut (if you pass something by reference to an algorithm, that algorithm shouldn't change it, clearly). This could still perhaps be made clearer in the standard... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17012
prev parent reply other threads:[~2005-07-05 12:11 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-12 19:57 [Bug c++/17012] New: " debrak at sgi dot com 2004-08-12 20:04 ` [Bug c++/17012] " giovannibajo at libero dot it 2004-08-12 20:11 ` pcarlini at suse dot de 2004-08-12 20:51 ` [Bug libstdc++/17012] " pcarlini at suse dot de 2004-08-12 21:07 ` debrak at sgi dot com 2004-08-12 21:20 ` pcarlini at suse dot de 2004-09-02 21:56 ` bkoz at gcc dot gnu dot org 2004-09-04 12:50 ` pcarlini at suse dot de 2004-09-05 9:42 ` caj at cs dot york dot ac dot uk 2004-09-05 11:41 ` caj at cs dot york dot ac dot uk 2004-09-17 14:21 ` pcarlini at suse dot de 2005-07-05 12:11 ` chris at bubblescope dot net [this message]
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=20050705121111.25348.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: 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).