From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9919 invoked by alias); 24 Jan 2002 21:57:04 -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 9887 invoked by uid 61); 24 Jan 2002 21:57:04 -0000 Date: Thu, 24 Jan 2002 13:57:00 -0000 Message-ID: <20020124215704.9886.qmail@sources.redhat.com> To: aaw@rincewind.tv, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: ljrittle@gcc.gnu.org Reply-To: ljrittle@gcc.gnu.org, aaw@rincewind.tv, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org X-Mailer: gnatsweb 2.9.3 Subject: Re: libstdc++/5475: std::locale not thread-safe; causes segmentation faults X-SW-Source: 2002-01/txt/msg00877.txt.bz2 List-Id: Synopsis: std::locale not thread-safe; causes segmentation faults State-Changed-From-To: open->closed State-Changed-By: ljrittle State-Changed-When: Thu Jan 24 13:57:04 2002 State-Changed-Why: Duplicate of libstdc++/5432. Patch for issue on mainline (FYI: solved using _Atomic_word instead of mutex). The included test case is exactly covered by thread/pthread3.cc . http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5475