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: 18 Oct 2006 10:40:22 -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 #4 from pcarlini at suse dot de 2006-10-18 10:40 -------
(In reply to comment #3)
> .... I'm
> only unsure about the tests "this->base() == __victim->base()", I hope can be
> done on the base objects too...
And of course it can't, such simply, the plain iterator info is necessary here,
because we want to change *all* iterators pointing the same as this->base()...
In case, looks like _M_invalidate needs a more complex interaction between
_Safe_iterator and _Safe_iterator_base...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29496