From: acs@acm.org
To: egcs@cygnus.com, gcc2@cygnus.com
Cc: Ronald Joe Record <rr@sco.com>, Robert Lipe <robertl@dgii.com>
Subject: egcs 10-31 and UnixWare
Date: Fri, 07 Nov 1997 09:25:00 -0000 [thread overview]
Message-ID: <199711071702.MAA14022@honeydew.icd.teradyne.com> (raw)
I still can't build the recent egcs snapshots on UnixWare 2.1.2 (SVR4.2 MP).
The most recent snapshot I successfully built was egcs-970910. I have tried
many snapshots since then, including 10-31 and 11-05 and they all fail in
the same way: the stage 1 compiler builds an executable which dumps core in
__do_global_dtors_aux() on the way out.
(testgcc-971104 fails in the same way, so I've included gcc2 in the
distribution list.)
Here's the backtrace:
#0 0xbffb3783 in kill ()
#1 0xbffe3528 in abort ()
#2 0x804853e in __do_global_dtors_aux ()
#3 0x8048ffd in _fini ()
(See http://www.cygnus.com/ml/egcs/1997-Oct/1099.html for more info.)
The failure comes from crtend.o. I'm trying to figure out what's going on
there, but I could use some pointers in how to debug it; gdb claims there is
no source information available for crtend.o.
BTW, I notice that crtstuff.c (progenitor of crtend.o) changed between
970910 and the newer snapshots to include a bunch of exception handling
code. (I mention this in case it jogs anyone's memory.) I also notice
that crtstuff.c is now identical between egcs and testgcc-971104.
Any hints/suggestions/reminders are welcome.
thanks,
vin shelton
next reply other threads:[~1997-11-07 9:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-07 9:25 acs [this message]
1997-11-09 10:14 ` Jeffrey A Law
1997-11-09 11:16 ` Robert Lipe
1997-11-09 13:49 ` Jeffrey A Law
1997-11-09 12:35 ` acs
1997-11-09 13:00 ` Robert Lipe
1997-11-09 17:00 ` Jeffrey A Law
1997-11-09 18:35 ` Joe Buck
1997-11-09 21:08 ` Joern Rennecke
1997-11-09 20:32 ` Robert Lipe
1997-11-10 14:57 ` H.J. Lu
1997-11-10 14:57 ` Robert Lipe
1997-11-10 12:27 ` H.J. Lu
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=199711071702.MAA14022@honeydew.icd.teradyne.com \
--to=acs@acm.org \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=robertl@dgii.com \
--cc=rr@sco.com \
/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).