From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14613 invoked by alias); 14 Jun 2007 02:56:47 -0000 Received: (qmail 14452 invoked by alias); 14 Jun 2007 02:56:36 -0000 Date: Thu, 14 Jun 2007 02:56:00 -0000 Message-ID: <20070614025636.14451.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/32261] Thread race segfault in std::string::append with -O and -s In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pinskia at gmail dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-06/txt/msg01094.txt.bz2 ------- Comment #7 from pinskia at gmail dot com 2007-06-14 02:56 ------- Subject: Re: Thread race segfault in std::string::append with -O and -s > bug 21334 seems to deal with multiple threads accessing the same shared object > at the same time. However, the sample code provided here involves separate > private objects so there should not be any such issues. If it is not possible > to assume that separate threads can access unrelated STL objects at the same > time, then this would imply that all STL operations (regardless of the object) > must be serialized! The empty string is the same object really. -- Pinski -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32261