From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17041 invoked by alias); 21 Jan 2002 21:51:07 -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 16966 invoked by uid 61); 21 Jan 2002 21:51:05 -0000 Date: Mon, 21 Jan 2002 13:51:00 -0000 Message-ID: <20020121215105.16965.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/msg00731.txt.bz2 List-Id: Synopsis: in multi-processor environment basic_string ist not thread safe Responsible-Changed-From-To: unassigned->ljrittle Responsible-Changed-By: ljrittle Responsible-Changed-When: Mon Jan 21 13:51:04 2002 Responsible-Changed-Why: Mine. State-Changed-From-To: open->feedback State-Changed-By: ljrittle State-Changed-When: Mon Jan 21 13:51:04 2002 State-Changed-Why: I couldn't reproduce this problem on a sparc-sun-solaris2.7 dual-processor machine against gcc 3.0.4 prerelease. I saw no boundless memory growth or crashes with 1 or 2 copies of the test program running. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5444