[Bug libstdc++/21772] New: exception safety testing allocator

[Bug libstdc++/21772] New: exception safety testing allocator

[bkoz at gcc dot gnu dot org]

Placeholder for exception-safety tests for STL components. 

The general technique I'd like to use is outlined by Matt. It's a throwing
allocator.

Ami has implemented this, nicely. I've attached it.

We need to integrate this into the testsuite, and make sure all containers are
testably eh-safe.

-benjamin

-- 
           Summary: exception safety testing allocator
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bkoz at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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

[Bug libstdc++/21772] exception safety testing allocator

[bkoz at gcc dot gnu dot org]

------- Additional Comments From bkoz at gcc dot gnu dot org  2005-05-26 17:07 -------
Created an attachment (id=8972)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8972&action=view)
pb_assoc's throwing allocator


-- 


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

[Bug libstdc++/21772] exception safety testing allocator

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2005-05-26 20:13 -------
Confirmed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-05-26 20:13:42
               date|                            |


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

[Bug libstdc++/21772] exception safety testing allocator

[bkoz at gcc dot gnu dot org]

------- Comment #8 from bkoz at gcc dot gnu dot org  2009-12-16 03:33 -------
Created an attachment (id=19319)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19319&action=view)
c++0x container requirement testing, eh


-- 


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

[Bug libstdc++/21772] exception safety testing allocator

[dave at boost-consulting dot com]

------- Comment #7 from dave at boost-consulting dot com  2007-05-27 23:07 -------
(In reply to comment #6)
> (In reply to comment #5)
> > Use this technique.  In fact, if you can, use my code.
> 
> In fact, Howard already mentioned that, at some point. To be clear, and avoid
> misunderstandings, I want to clearly state that I consider your offer very
> kind. Thanks. However, the normal way to manage that would be you filing a
> copyright assignment and the contributing the code, with full acknowledgment of
> your help. I'm not sure we can "speed-up" the procedure much... 

OK, please send me a private email pointing to how to file such an assignment.
Note also that the code may have been modified by others and IIRC it doesn't
exactly test the current standard guarantees, so it will need to be worked
over.


-- 


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

[Bug libstdc++/21772] exception safety testing allocator

[pcarlini at suse dot de]

------- Comment #6 from pcarlini at suse dot de  2007-05-21 18:12 -------
(In reply to comment #5)
> Use this technique.  In fact, if you can, use my code.

In fact, Howard already mentioned that, at some point. To be clear, and avoid
misunderstandings, I want to clearly state that I consider your offer very
kind. Thanks. However, the normal way to manage that would be you filing a
copyright assignment and the contributing the code, with full acknowledgment of
your help. I'm not sure we can "speed-up" the procedure much... 


-- 


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

[Bug libstdc++/21772] exception safety testing allocator

[dave at boost-consulting dot com]

------- Comment #5 from dave at boost-consulting dot com  2007-05-21 17:16 -------
Just "adding a throwing allocator" (especially one that throws
randomly like this one) will not test the library guarantees anywhere
nearly as effectively as the STLPort tests do.  The technique is
outlined in http://www.boost.org/more/generic_exception_safety.html

Use this technique.  In fact, if you can, use my code.


-- 


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

[Bug libstdc++/21772] exception safety testing allocator

[bkoz at gcc dot gnu dot org]

------- Comment #4 from bkoz at gcc dot gnu dot org  2007-05-21 15:58 -------

This is now integrated, but the tests are still ad-hoc. We need a more
consistent application of eh-safety tests.


-- 


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

[Bug libstdc++/21772] exception safety testing allocator

[pcarlini at suse dot de]

------- Comment #3 from pcarlini at suse dot de  2007-05-21 09:26 -------
Also see libstdc++/32017 for some additional details.


-- 


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