From: Frank Ecke <franke@euro-telematik.de>
To: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
Cc: gcc <gcc@gcc.gnu.org>, Arnaud Charlet <charlet@ACT-Europe.FR>
Subject: Re: Building the Ada compiler... is http://gcc.gnu.org/install/build.html correct?
Date: Sat, 17 Jul 2004 21:06:00 -0000 [thread overview]
Message-ID: <200407171527.i6HFRrK9005086@mail.euro-telematik.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Upon Nov 5, 2003, Rainer Orth spake unto us thuswise, saying:
> Currently I try to get it working on IRIX 6.2/6.5. While the compiler
> proper bootstraps with the change suggested in PR middle-end/6552, make
> gnatlib_and_tools only builds the runtime library successfully. The
> freshly built gnatmake prints
> __exc_unwind: Error: pc(0x1021075c) not in any .debug_frame table
> and just hangs.
I have experienced the same with GCC 3.3.3 and 3.3.4; only in my
case, the freshly built gnatmake doesn't hang but causes a
segmentation fault and produces a core dump:
../../gnatmake -c -I../rts -I. -I/usr/people/franke/install/srcdir/gcc/ada gnatchop --GCC="../../xgcc -B../../ -g -gnatpg -gnata"
__exc_unwind: Error: pc(0x102aa700) not in any .debug_frame table
__exc_unwind: Error: pc(0x102aa70c) not in any .debug_frame table
__exc_unwind: Error: pc(0x102aa70c) not in any .debug_frame table
__exc_unwind: Error: pc(0x102aa70c) not in any .debug_frame table
__exc_unwind: Error: pc(0x102aa70c) not in any .debug_frame table
[snip]
__exc_unwind: Error: pc(0x102aa70c) not in any .debug_frame table
__exc_unwind: Error: pc(0x102aa70c) not in any .debug_frame table
make[2]: *** [../../gnatchop] Segmentation fault (core dumped)
make[2]: Leaving directory `/usr/people/franke/install/objdir/gcc/ada/tools'
make[1]: *** [gnattools2] Error 2
make[1]: Leaving directory `/usr/people/franke/install/objdir/gcc/ada'
make: *** [gnattools] Error 2
(glanzer 718) $
In addition to that, I've found the following in the system's
log:
Jul 17 16:36:31 4A:glanzer unix: WARNING: Process gnatmake pid 2171 referenced bad addr 0xc0000fc00050fa38
For my little SGI, this is clearly out of reach, :-(
> This error is from the IRIX 6 libexc.so. I have no idea
> what to do about this and haven't yet tried debugging what's going on
> here.
Has anyone been able to shed some light on this issue in the
meantime?
Regards,
Frank
- --
Frank Ecke <franke@euro-telematik.de>, see pgpkeys.mit.edu:11371
Fingerprint = 2CCD 7D50 E07E 557E EA2F 7454 068C B20A 20FF C83D
Bradley's Bromide:
If computers get too powerful, we can organize them into a
committee---that will do them in.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (IRIX64)
iD8DBQFA+USbBoyyCiD/yD0RAkeJAJ43tNNb+aHcRNS+3QNNTlC1cfCDwACgge0P
t7i7x0AnfsusRohBtnCxVR0=
=XLFu
-----END PGP SIGNATURE-----
next reply other threads:[~2004-07-17 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 21:06 Frank Ecke [this message]
2004-07-19 13:52 ` Rainer Orth
2004-08-14 18:23 ` Frank Ecke
-- strict thread matches above, loose matches on Subject: below --
2003-11-05 16:07 Christian Joensson
2003-11-05 18:06 ` Rainer Orth
2003-11-05 18:22 ` Joseph S. Myers
2003-11-05 19:02 ` Rainer Orth
2003-11-06 14:14 ` Arnaud Charlet
2003-11-06 18:18 ` Rainer Orth
2003-11-06 21:05 ` Toon Moene
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=200407171527.i6HFRrK9005086@mail.euro-telematik.de \
--to=franke@euro-telematik.de \
--cc=charlet@ACT-Europe.FR \
--cc=gcc@gcc.gnu.org \
--cc=ro@TechFak.Uni-Bielefeld.DE \
/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).