This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libstdc++/29496] _M_invalidate function is not thread-safe in GLIBCXX_DEBUG mode



------- Comment #7 from l_heldt at poczta dot onet dot pl  2006-10-19 13:51 -------
(In reply to comment #2)
> Please attach a complete test case, not a sketch.
> 
> -benjamin
> 

This bug is a pure race-condition. There is no test case which would reveal it
with a 100% certainty. I have noticed the bug after receiving strange SIGSEGV
in _M_invalidate() function. After reviewing the code I found the problem
stated in this bug report.

Of course you can say: "No test case - no bug" but I guess this would be a very
naive approach.


-- 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]