From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22777 invoked by alias); 22 Jan 2002 22:13:22 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 22727 invoked by uid 61); 22 Jan 2002 22:13:21 -0000 Date: Tue, 22 Jan 2002 14:13:00 -0000 Message-ID: <20020122221320.22726.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ljrittle@gcc.gnu.org, markus.breuer@materna.de, nobody@gcc.gnu.org From: ljrittle@gcc.gnu.org Reply-To: ljrittle@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ljrittle@gcc.gnu.org, markus.breuer@materna.de, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org X-Mailer: gnatsweb 2.9.3 Subject: Re: libstdc++/5444: in multi-processor environment basic_string ist not thread safe X-SW-Source: 2002-01/txt/msg00795.txt.bz2 List-Id: Synopsis: in multi-processor environment basic_string ist not thread safe Responsible-Changed-From-To: ljrittle->unassigned Responsible-Changed-By: ljrittle Responsible-Changed-When: Tue Jan 22 14:13:19 2002 Responsible-Changed-Why: Doesn't look as related to the part of the code base I understand as I originally thought. State-Changed-From-To: feedback->analyzed State-Changed-By: ljrittle State-Changed-When: Tue Jan 22 14:13:19 2002 State-Changed-Why: Agreed, I can reproduce the reduced test case failure on a two-way MP sparc-sun-solaris2.7 machine using gcc 3.0.3+"sparc atomicity patch". Parts of the reduced test case violate libstdc++-v3 threading rules but I agree that ``std::ostringstream oss'' should be concurrently executable in different threads and is the root cause of a core dump. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5444