John Stutz writes:
Matlab-mode having recently developed the 'File mode
specification
error:'
XEmacs 21.4 is over 10 years old; the :visible keyword was not
implemented then, I suppose, and new feature development is all done
in the 21.5 branch since about 2001.
below, I have been trying to track down where things are going
astray. I
believe this crash occurred while closing down one copy of Xemacs. I hav eno
good idea of how to reproduce it.
Without a C backtrace, there is essentially no way to diagnose a
crash. If core files are enabled, you can get the C backtrace with
"gdb `which xemacs` COREFILE" (sorry, I don't know where Fedora keeps
its core files), and typing "bt" to the (gdb) prompt. Copy/paste from
the terminal output. On Fedora to get a useful backtrace you will
need to install the xemacs debug package, which installs the symbol
table for your binary (I'm not sure what it's called), and you may
need to specify the symbol file explicitly to gdb with the
"--symbols=SYMBOLFILE" option.
Otherwise, you can run XEmacs under gdb with "gdb `which xemacs`"
which will allow you to get a backtrace in the future. (The caveat
about the debug package and the symbol file applies here, too.) This
does not slow down XEmacs but does tie up a terminal window. (If you
use "xemacs -nw" and run in a terminal window, you also have to be
careful of interrupt characters, specifically C-z and multiple C-g in
quick succession. The exact effect depends on the configuration of
gdb.)
I recommend that you upgrade to the most recent XEmacs 21.4 at
least (ISTR that a crash was fixed in that version).
For more modern features, you might want to upgrade to XEmacs 21.5
(beta32 was released yesterday). Although there remains a lot of work
to fully implement GNU compatibility, XEmacs 21.5 is very stable in
use.
I fail to find the PROBLEMS file referenced in the error message.
It's probably in /usr/share/xemacs-21.4.20/etc/PROBLEMS.
I fail to find the C stack back trace file referenced in the error
message, even when using find to locate all recently altered files.
It's not possible to generate a C backtrace without a debugger.
[jstutz@sessile ~]$ WARNING: Unable to auto-save your files
properly.
Some or all may in fact have been auto-saved.
This is very bad. I've never seen it personally. Make that "strongly
recommend" an upgrade. Anything that interferes with autosave is
worth a fair amount of effort to avoid.
next-window(nil)
I don't think I've ever seen a crash from this function. I'll keep it
in mind, but this doesn't help localize the cause crash.
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta