[Bug optimization/11386] GNU Emacs 21.3 failed to install using GCC 3.3, but GCC 3.2.3 works.

[ishikawa at yk dot rim dot or dot jp]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11386



------- Additional Comments From ishikawa at yk dot rim dot or dot jp  2003-07-03 18:18 -------
emacs segfaulting at exit time after doing nothing!?

I also found that during boostrapping emacs, bootstrap-emacs, which is
created using
bootstrap-emacs: bootstrap-temacs bootstrap-doc
       ./temacs --batch --load loadup bootstrap
       mv -f emacs bootstrap-emacs
       rm -f temacs

which means that the executables, both emacs and bootstrap-emacs seem to be
mangled AFTER
unexec() in emacs-21.3/src/unexelf.c.
(non-initialized Emacs does so many initial data loading (emacs lisp
libraries getting loaded), that once the internal state is reached,
the image of the process is dumped into an external file, which
becomes the executable file that users will use.

So comes the question. Has there been a change between
GCC 3.2.3 and GCC 3.3
in the area of memory layout of the GCC startup code (or for that matter,
a generic memory layout of the GCC produced code)?

unexec(), which produces the clone of the
running image,  is highly dependent on the executable format and
the implicit assumptions made by the startup code, etc.

That we are seeing  segmentation fault in __do_global_ators() 
highly suggests that unexec() is now broken somehow.