public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "delong.j at fb dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/50529] New: std::vector::erase invokes undefined behavior with empty range
Date: Tue, 27 Sep 2011 00:45:00 -0000	[thread overview]
Message-ID: <bug-50529-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50529

             Bug #: 50529
           Summary: std::vector::erase invokes undefined behavior with
                    empty range
    Classification: Unclassified
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: delong.j@fb.com


If you call vector erase() with an empty range, it invokes std::move() with an
output iterator inside of the source range.  (I.e. it tries to move all the
elements onto themselves.)  This causes problems if some of the elements don't
support self move-assignment (e.g. if they are other std::vectors).


             reply	other threads:[~2011-09-27  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27  0:45 delong.j at fb dot com [this message]
2011-09-27  1:56 ` [Bug libstdc++/50529] [C++0x] " paolo.carlini at oracle dot com
2011-09-27  1:57 ` paolo.carlini at oracle dot com
2011-09-27  2:56 ` paolo at gcc dot gnu.org
2011-09-27  4:15 ` paolo.carlini at oracle dot com
2011-09-27  7:56 ` delong.j at fb dot com
2011-09-30 21:16 ` paolo at gcc dot gnu.org
2011-09-30 23:36 ` paolo.carlini at oracle dot com

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=bug-50529-4@http.gcc.gnu.org/bugzilla/ \
    --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).