From: Jeff Sturm <jsturm@one-point.com>
To: ultralinux@vger.kernel.org
Subject: Re: libstdc++ bus errors
Date: Tue, 13 Nov 2001 05:20:38 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-100562883822802@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-100562646118090@msgid-missing>
On Mon, 12 Nov 2001, Sean Callanan wrote:
> I am currently rebuilding my system from scratch (using the instructions at
> www.linuxfromscratch.org) with GCC 3.0.2 and glibc 2.2.4.
> I have simply compiled GCC 3.0.2 for sparc-linux (32-bit) with dynamic
> linking against the new libc. However, even a test program:
> --
> #include <iostream.h>
>
> void main()
> {
> cout << "Hello C++!\n";
> exit(0);
> }
> --
> has a bus error. Are there known issues with sparc and libstdc++ 3.0.2?
> (Incidentally, I try to run the library itself, and get a segmentation
> fault, but I suspect that isn't such a big issue since the c++ library on
> my original SuSE install does the exact same thing.
I've seen this too, using slackware-current on sparc. The cause is
twofold: GNU ld incorrectly generates a R_SPARC_32 reloc for an unaligned
word, which ld.so cannot fix because unaligned stores cause a trap on
sparc.
Upgrading binutils to 2.11.2 doesn't solve the problem, because ld.so
doesn't understand R_SPARC_UA32 relocations:
./a.out: error while loading shared libraries: /home/jsturm/junk.so:
unexpected reloc type 0x17
Before I tackle it, anyone know if there is a fixed libc for sparc-linux?
(Meanwhile, configuring gcc with --enable-sjlj-exceptions might be an
effective workaround.)
Jeff
next prev parent reply other threads:[~2001-11-13 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 4:39 libstdc++ bus errors Sean Callanan
2001-11-13 5:20 ` Jeff Sturm [this message]
2001-11-13 5:33 ` David S. Miller
2001-11-13 6:00 ` Jeff Sturm
2001-11-14 17:15 ` sc843
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=marc-linux-ultrasparc-100562883822802@msgid-missing \
--to=jsturm@one-point.com \
--cc=ultralinux@vger.kernel.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