please note:
the crash occurs very early when running the dumped executable.
it occurs in CHECK_SYMBOL (alias) in Fdefine_coding_system_alias(), called from
determine_if_using_unicode(), from init_intl_win32(), called early at startup.
the value of the variable appears to be garbage. in fact, all dumped variables
appear to have garbage values. stop at the first line of code, e.g., and you'll
see that noninteractive has some large, garbage value instead of something like
0 or 1.
perhaps the crash is occurring at the first point that XEmacs does an indirect
memory access through any value that should have been remembered across the
dumping probcess.
----- Original Message -----
From: "Ben Wing" <ben(a)666.com>
To: "XEmacs beta list" <xemacs-beta(a)xemacs.org>;
<xemacs-winnt(a)xemacs.org>
Cc: <sos(a)prospect.com.ru>
Sent: Wednesday, February 19, 2003 2:30 AM
Subject: unable to build cygwin, traditional dumping + sysmalloc (+ others?)
two of my nine builds, each with various different options, crash
under
Cygwin.
I can narrow it down to a crash that occurs with a plain configure, adding
only
sysmalloc. taking away sysmalloc and adding noerror, for example,
and no more
crash. same just take away sysmalloc and add nothing, far as i can tell.
adding pdump also makes the crash go away.
any Cygwin/GCC gurus out there who can tell me what's up? Someone -- Sergey
Okhapkin <sos(a)prospect.com.ru> -- recently fixed up the traditional dumping
support for GCC 3.
Sergey, any help?
if we don't find the answer, it should probably go into PROBLEMS.
thanks, ben