From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25150 invoked by alias); 12 Jun 2007 01:36:19 -0000 Received: (qmail 25124 invoked by uid 48); 12 Jun 2007 01:36:10 -0000 Date: Tue, 12 Jun 2007 01:36:00 -0000 Message-ID: <20070612013610.25123.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/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: "jlawson-gcc at bovine dot net" 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/msg00843.txt.bz2 ------- Comment #3 from jlawson-gcc at bovine dot net 2007-06-12 01:36 ------- This seems like a rather unexpected crash given the seemingly valid example code. Can anyone from the GCC team indicate the actual compiler issue that might cause this example to fail, and specifically indicate an existing bugzilla number that addressed it? I'm worried that this issue may very well have been unintentionally hidden and not actually fixed. (For example, a casual code change might have altered segment alignments and symbol offsets happen to overflow differently.) -- jlawson-gcc at bovine dot net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlawson-gcc at bovine dot | |net http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32261