* [Bug libstdc++/52447] Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8
2012-03-01 10:48 [Bug libstdc++/52447] New: Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8 john.unsworth at criticalpath dot net
@ 2012-03-01 11:13 ` redi at gcc dot gnu.org
2012-03-01 11:14 ` redi at gcc dot gnu.org
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: redi at gcc dot gnu.org @ 2012-03-01 11:13 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52447
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |4.3.2
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-03-01 11:13:15 UTC ---
6.0.10 is from GCC 4.3 which is no longer supported here, if you want a change
to that version you should report it to SUSE
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug libstdc++/52447] Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8
2012-03-01 10:48 [Bug libstdc++/52447] New: Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8 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
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: redi at gcc dot gnu.org @ 2012-03-01 11:14 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52447
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-03-01 11:14:26 UTC ---
Also, nothing will happen without a testcase to reproduce the problem, see
http://gcc.gnu.org/bugs/
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug libstdc++/52447] Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8
2012-03-01 10:48 [Bug libstdc++/52447] New: Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8 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
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: rguenth at gcc dot gnu.org @ 2012-03-01 11:34 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52447
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2012-03-01
Ever Confirmed|0 |1
--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-01 11:34:26 UTC ---
Also as you report the issue for two different vendor versions it is necessary
to known how GCC (and thus libstdc++) was configured.
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug libstdc++/52447] Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8
2012-03-01 10:48 [Bug libstdc++/52447] New: Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8 john.unsworth at criticalpath dot net
` (2 preceding siblings ...)
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
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: john.unsworth at criticalpath dot net @ 2012-03-01 11:49 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52447
--- Comment #4 from John Unsworth <john.unsworth at criticalpath dot net> 2012-03-01 11:49:12 UTC ---
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?
Producing a test case will be hard because it is a large application using many
shared libraries.
Thank you.
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug libstdc++/52447] Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8
2012-03-01 10:48 [Bug libstdc++/52447] New: Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8 john.unsworth at criticalpath dot net
` (3 preceding siblings ...)
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
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: rguenth at gcc dot gnu.org @ 2012-03-01 12:06 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug libstdc++/52447] Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8
2012-03-01 10:48 [Bug libstdc++/52447] New: Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8 john.unsworth at criticalpath dot net
` (4 preceding siblings ...)
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
2012-05-02 17:13 ` bkoz at gcc dot gnu.org
7 siblings, 0 replies; 9+ messages in thread
From: john.unsworth at criticalpath dot net @ 2012-03-01 12:16 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52447
--- Comment #6 from John Unsworth <john.unsworth at criticalpath dot net> 2012-03-01 12:16:18 UTC ---
The application is 32 bit and we build on a 32 bit linux Linux version
2.6.9-89.ELsmp. We are running on 64 bit SLES11.
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug libstdc++/52447] Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8
2012-03-01 10:48 [Bug libstdc++/52447] New: Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8 john.unsworth at criticalpath dot net
` (5 preceding siblings ...)
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
7 siblings, 0 replies; 9+ messages in thread
From: bkoz at gcc dot gnu.org @ 2012-04-25 2:35 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Bug libstdc++/52447] Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8
2012-03-01 10:48 [Bug libstdc++/52447] New: Application crashes on SLES11 when using libstdc++.so.6.0.10 but runs fine with 6.0.8 john.unsworth at criticalpath dot net
` (6 preceding siblings ...)
2012-04-25 2:35 ` bkoz at gcc dot gnu.org
@ 2012-05-02 17:13 ` bkoz at gcc dot gnu.org
7 siblings, 0 replies; 9+ messages in thread
From: bkoz at gcc dot gnu.org @ 2012-05-02 17:13 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52447
Benjamin Kosnik <bkoz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |WORKSFORME
--- Comment #8 from Benjamin Kosnik <bkoz at gcc dot gnu.org> 2012-05-02 17:13:08 UTC ---
Re-open if present in self-contained testcase.
^ permalink raw reply [flat|nested] 9+ messages in thread