From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-218820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 8870 invoked by alias); 21 May 2007 04:49:59 -0000
Received: (qmail 8843 invoked by uid 48); 21 May 2007 04:49:47 -0000
Date: Mon, 21 May 2007 04:49:00 -0000
Subject: [Bug libstdc++/32017]  New: Exception-safety bug
X-Bugzilla-Reason: CC
Message-ID: <bug-32017-501@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "dave at boost-consulting dot com" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2007-05/txt/msg01685.txt.bz2

list<T>::insert(pos, start, finish) doesn't provide the strong guarantee as
required by 23.2.3.3 list modifiers

See
http://groups.google.com/group/comp.lang.c++.moderated/browse_frm/thread/b215edcb44b19bb9/c875353acb4da29e

It's almost a sure bet that libstdc++ contains other exception-safety bugs.

I suggest you adapt and adopt the test mentioned here:
http://groups.google.com/group/comp.lang.c++.moderated/tree/browse_frm/thread/1ff1165766b913f5/92dcc2c639b9ce39
and here:
http://groups.google.com/group/comp.lang.c++.moderated/browse_frm/thread/5272e2a3501ad534/3c80688532fcf240


-- 
           Summary: Exception-safety bug
           Product: gcc
           Version: 4.1.2
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dave at boost-consulting dot com
  GCC host triplet: i486-linux-gnu
GCC target triplet: i486-linux-gnu


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