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: "l_heldt at poczta dot onet dot pl" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Oct 2006 17:23:53 -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 #20 from l_heldt at poczta dot onet dot pl 2006-10-31 17:23 -------
(In reply to comment #16)
> (In reply to comment #15)
> > I tried to prepare a simple testcase but without any success. It seems to be
> > extremely hard to hit the moment when pointers are actually changed. Trivial
> > programs do not reveal the problem.
>
> Ok, but you should try harder, because often in the past we managed to prepare
> complete testcases for races and generally MT issues too, which seemed very
> tricky at the outset.
>
I think we are totally misunderstood here. I don't have time to prepare complex
test cases revealing problems not in my code. I have found the bug I even found
the cause of the bug and it is still not enough for you.
If you don't want to be informed about problems in stl then what is this
bugzilla for?
I have already made a workaround in my code to avoid the debug container in
certain situations so it's not me who will actually benefit from the fix.
I reported this issue to help other developers who might encounter similar
problem.
Because of version policies in my company probably I won't be even able to use
your fix.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29496