From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11364 invoked by alias); 25 Apr 2012 02:35:36 -0000 Received: (qmail 11297 invoked by uid 22791); 25 Apr 2012 02:35:35 -0000 X-SWARE-Spam-Status: No, hits=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 25 Apr 2012 02:35:23 +0000 From: "bkoz at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/52447] Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8 Date: Wed, 25 Apr 2012 02:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: bkoz at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: CC Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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: 2012-04/txt/msg02199.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52447 Benjamin Kosnik changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bkoz at gcc dot gnu.org --- Comment #7 from Benjamin Kosnik 2012-04-25 02:35:21 UTC --- Hmm. Reviewing this bug report, I see static initialization issues in large C++ projects, with many dependencies, involving three older and unsupported (from the FSF perspective) toolchains, and no testcase. To review: gcc-3.4 ish = 6.0.3 gcc-4.1 ish = 6.0.8 gcc-4.3 ish = 6.0.10 Static locals got reworked at 4.0, so if you can run w/o error on 6.0.8 it's probably not that. (Behaviour can be reverted w/ -fno-threadsafe-statics if you are feeling like testing this.) Without additional input, we're not going to be able to help you resolve this, sorry. That might be ok for you, if this was just a general "is this supposed to work/are there known bugs" query. You have an answer. If you are trying to get to the bottom of this, here are some things that might be useful: 1) a way to reproduce, using one of the toolchain releases that is marked as active on the gcc web site. Without this, I'm afraid we'll have to close this bug report, and intend to do so after May 1, 2012. 2) porting to gcc-4.4/libstdc++.so.6.0.11+, instead of gcc-4.3. Gcc-4.4 was a more widely deployed gcc release, and it is likely that integration issues with the older (at this point, quite old) system environment may be better understood. Those packages might be more polished, so maybe you'll just get lucky. You might want to see if SLES 11 has an alternate/newer compiler packaged directly by the vendor, or use the opensuse gcc44 package. There may be a subtle integration issue unknown to you.