public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth 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: Thu, 01 Mar 2012 12:06:00 -0000 [thread overview]
Message-ID: <bug-52447-4-ZutdSsaEzw@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
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |i?86-*-*
--- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-01 12:05:29 UTC ---
(In reply to comment #4)
> Can you confirm that applications built on Red Hat with:
>
> Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.6/specs
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --disable-checking --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.4.6 20060404 (Red Hat 3.4.6-11)
>
> should work on SLES 11 with the standard libstdc++ on that system which is
> 6.0.10? Or do we need to ensure that 6.0.8 is used?
SLE11 SP1 gcc is configured like
../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man
--libdir=/usr/lib --libexecdir=/usr/lib
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.3
--enable-ssp --disable-libssp --with-bugurl=http://bugs.opensuse.org/
'--with-pkgversion=SUSE Linux' --disable-libgcj --disable-libmudflap
--with-slibdir=/lib --with-system-zlib --enable-__cxa_atexit
--enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --program-suffix=-4.3
--enable-linux-futex --without-system-libunwind --with-cpu=generic
--build=i586-suse-linux
which looks compatible. So yes, it should work.
I am assuming you are on a 32bit host. Please clarify if you built
on a 32bit host but are running on a 64bit host with 32bit libs.
> Producing a test case will be hard because it is a large application using many
> shared libraries.
It might be that the new libstdc++ uses TLS for thread-safe init and the
old one not and that you are hitting a dynamic linker bug so that TLS is
not properly initialized when the application dlopens libmuwssoap.so.
You have to debug this further yourself if you do not have a testcase.
next prev parent reply other threads:[~2012-03-01 12:06 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 [this message]
2012-03-01 12:16 ` john.unsworth at criticalpath dot net
2012-04-25 2:35 ` bkoz at gcc dot gnu.org
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-ZutdSsaEzw@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).