Itamar Glatzer writes:
I tryed to close my emacs when there was unsaved file. A GUI massage
appeared asking me if I want to save the file (as always in this
case). I pressed on the 'x' bottom in the top of the GUI and then the
emaxs has crashed.
XEmacs is very old, and many crashes have been fixed since then.
There's no information in your post that would help to identify the
problem, so at this point all we can do is recommend upgrading to
21.4.20.
The core file is attached
Fortunately, you seem to have forgotten to send it. The proper way to
send a core file is by airmail, on the hard disk, in the machine where
the crash occurred. I don't think you want to do that....
If you still have the corefile, it would be very helpful if you would
run a debugger on the xemacs executable that crashed, reading program
state from the corefile. Obtain a backtrace of stack frames and send
that to us. It is very important that the backtrace include symbolic
information; since you appear to be using a precompiled binary, it may
not be immediately available. In that case, your vendor may make a
separate debug executable or symbol table available in an xemacs-debug
package (or something like that).
If you are not familiar with debuggers, the procedure is
straightforward and explained in the Bugs node of the Info manual,
which you can read using C-h i in XEmacs. If for some reason you have
trouble accessing Info, some other ways of obtaining the information
are given in the file BUGS which should be in the XEmacs documentation
on your system.
HTH
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta