From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8251 invoked by alias); 31 Oct 2006 17:24:05 -0000 Received: (qmail 8154 invoked by uid 48); 31 Oct 2006 17:23:53 -0000 Date: Tue, 31 Oct 2006 17:24:00 -0000 Message-ID: <20061031172353.8153.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/29496] _M_invalidate function is not thread-safe in GLIBCXX_DEBUG mode In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "l_heldt at poczta dot onet dot pl" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-10/txt/msg02716.txt.bz2 List-Id: ------- 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