RE: unexelf.c maybe broke between 21.1 and 21.2

[Horsley Tom <Tom.Horsley@ccur.com>]

> > The unexelf.c in emacs-21.2 fails to build a functional object file on
my
> > system. The resulting emacs always coredumps because none of its globals
> > actually have correctly initialized values in them.
> 
> Thank you for your report, but please tell what system is that.  (M-x 
> report-emacs-bug RET would provide this and other relevant info.)

I could tell you, but it wouldn't really help because it isn't a system
that emacs knows about anyway :-). (It is far less trouble to apply the
patches to each releases configure scripts than to try to find all the
lawyers I need to submit the patches permanently to the FSF).

However, here is what it reports:

In GNU Emacs 21.2.2 (powerpc-concurrent-powermax, Motif Version 2.1.0)
 of 2002-08-28 on amber2
configured using `configure  --prefix=/usr/tools/emacs-21.2 --with-x
--with-x-toolkit=motif --x-libraries=/usr/lib --x-includes=/usr/include'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: nil
  locale-coding-system: nil
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

All I know for sure is that if I debug temacs and stop at the beginning
of the unexec routine, I can look at various local variables
(like Vmessage_buffer_name, etc) and see reasonable values.

If I debug emacs and look at the same global variables, they
contain trash.