This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/29496] _M_invalidate function is not thread-safe in GLIBCXX_DEBUG mode
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Nov 2006 22:42:28 -0000
- Subject: [Bug libstdc++/29496] _M_invalidate function is not thread-safe in GLIBCXX_DEBUG mode
- References: <bug-29496-9884@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #22 from pcarlini at suse dot de 2006-11-01 22:42 -------
Created an attachment (id=12531)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12531&action=view)
All the functions working on a set of _Safe_iterators fixed
In my present understanding *all* the functions belonging to
_Safe_iterator_base, _Safe_iterator, _Safe_sequence_base, and _Safe_sequence
going through a full set of iterators attached to a container are currently
weak wrt the scenario presented in this PR, where _M_detach is called by
iterator destructor. This new draft patch reflects that, consistently. I'm
currently testing it, so far everything seems ok on x86-linux and ia64-linux
four-way.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29496