This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: i386-pc-solaris2.5.1: recent snapshots can't build emacs-20.2
- To: law at cygnus dot com
- Subject: Re: i386-pc-solaris2.5.1: recent snapshots can't build emacs-20.2
- From: "David S. Miller" <davem at dm dot cobaltmicro dot com>
- Date: Fri, 17 Jul 1998 09:36:18 -0700
- CC: meyering at ascend dot com, egcs at cygnus dot com, rms at gnu dot org
- References: <29026.900692049@hurl.cygnus.com>
Date: Fri, 17 Jul 1998 10:14:09 -0600
From: Jeffrey A Law <law@hurl.cygnus.com>
Based on the info I've seen I'd bet the first word is nonzero, but
the second word is zero, causing __do_global_ctors_aux to jump to
zero. This would most likely indicate an unexec problem of some
kind.
It could be that unexecelf is being confused by the ELF layouts which
egcs produces in the executable. Essentially unexecelf just figures
out the live ELF section boundaries, extends the BSS to include the
lisp code loaded in, and dumps these into the resulting executable.
There are two areas which might prove fruitful to investigate:
1) Do the resulting executables violate some of the assumptions
about how certain text/data/bss symbols represent the boundaries of
said sections?
2) Is the dwarf2 unwind info on x86 creating ELF object files which
confuse unexelf in some way to output corrupt images?
In any event, it appears that the bug I have seen wrt. emacs builds
with egcs, and the one being seen here on x86 are two seperate bugs.
This I am sure of.
Later,
David S. Miller
davem@dm.cobaltmicro.com