public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu.org" <gcc-bugzilla@gcc.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 [thread overview]
Message-ID: <bug-52447-4-9BipPCsDXE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52447-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52447
Benjamin Kosnik <bkoz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bkoz at gcc dot gnu.org
--- Comment #7 from Benjamin Kosnik <bkoz at gcc dot gnu.org> 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.
next prev parent reply other threads:[~2012-04-25 2:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 10:48 [Bug libstdc++/52447] New: " john.unsworth at criticalpath dot net
2012-03-01 11:13 ` [Bug libstdc++/52447] " redi at gcc dot gnu.org
2012-03-01 11:14 ` redi at gcc dot gnu.org
2012-03-01 11:34 ` rguenth at gcc dot gnu.org
2012-03-01 11:49 ` john.unsworth at criticalpath dot net
2012-03-01 12:06 ` rguenth at gcc dot gnu.org
2012-03-01 12:16 ` john.unsworth at criticalpath dot net
2012-04-25 2:35 ` bkoz at gcc dot gnu.org [this message]
2012-05-02 17:13 ` bkoz at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-52447-4-9BipPCsDXE@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).