This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: target/8004: All C++ binaries crash in__register_frame_info_bases on Sparc Solaris 2.7
- From: "David S. Miller" <davem at redhat dot com>
- To: aaron_williams at net dot com
- Cc: davem at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
- Date: Tue, 01 Oct 2002 21:50:49 -0700 (PDT)
- Subject: Re: target/8004: All C++ binaries crash in__register_frame_info_bases on Sparc Solaris 2.7
- References: <20021002035926.24627.qmail@sources.redhat.com><3D9A724F.1070804@net.com>
From: "Aaron Williams" <aaron_williams@net.com>
Date: Tue, 01 Oct 2002 21:13:03 -0700
I should have all the required patches installed. I have Sun's patch
cluster as of 9/11 installed. I believe this may be due to a bug in
ld.so. I am attaching a copy of an email I received from someone else
who appears to have the same problem. My current workaround is to use
Sun's /usr/ccs/bin/ld instead of the one from binutils 2.13.
Binutils version 2.13 is known to cause major problems for Solaris
users.
I am having other stability problems with gcc 3.2 on Solaris and will
likely go back to 2.95.3. Konqueror in KDE 3.0.3 and qt-3.0.5 compiled
with gcc 3.2 is unstable, for example. I was hoping 3.2 would fix a
problem where I see static destructors being called in a shared library
when the shared library is no longer present (causing a crash in the
exit handler). This too, unfortunately sound like it might be a Solaris
bug.
You may have more success using binutils-2.12