xemacs crash

[Stephen J. Turnbull]

Samuel Bronson writes:

 > Fatal error.

Huh, no error code or line number, etc?

 >   # bind (print-message-label)
 >   error-message-string((wrong-type-argument
 > 
 > and it breaks off there, as if it had either crashed in the midst of
 > printing this line or not been able to flush the rest.

That does look look a crash in the error-reporting mechanism (perhaps
during an attempted shutdown after an earlier crash).

Is this repeatable?

 > VC++ could only give me the following "stack trace"; I'm not sure how
 > reliable it is. (I do also have a minidump if someone wants to take a
 > look at that, but it's 10 megs, so I'm not attaching it to this
 > message.)
 > >	xemacs.exe!011a7fbe() 	
 >  	xemacs.exe!0118ebc1() 	

This is strange.  Windows backtraces usually have stack frame
information, I thought, such as names of called functions and
arguments.  Without that, I don't think we can do much.

Are you stripping symbols out of the binary?

Hopefully one of the Windows people will speak up; that about exhausts
my knowledge (cough) of debugging crashes on Windows.