Stefan Alfredsson writes:
I was asked to write a bug report to you after an xemacs session
crashed. I opened the file main.tex some days ago, left the editor
idle, and when I started typing again it crashed. It's a standard
install from Ubuntu 8.04 on the AMD64 platform.
This is the terminal output: [own comments in brackets]
$ xemacs21 main.tex
[application active for a few days]
Fatal error (11).
This is a segmentation violation, which means it's probably a genuine
XEmacs bug. However, it could be in one of the supporting libraries,
such as libpng. This normally would not occur after a period of
inactivity, but rather when a "bad" image file was loaded, though.
Problems in X libraries (which are asynchronous) might occur this way,
but it's not possible to be sure without a stack trace.
*Please* try *hard* to obtain a C stack backtrace; without it, we
are unlikely
[sorry, I had ulimit -c 0 set, so no coredump available]
Since you are using a stripped binary with no debugging information
available at all, there is essentially zero chance of debugging this
crash.
If you wish to help to debug it, you should find out if your vendor
provides an XEmacs debugging package which includes the symbol table
for XEmacs. If so, you can install that, and either enable core dumps
or (better yet) run XEmacs under the debugger. Then continue working
until XEmacs crashes again (possibly a long time from now), and report
the stack trace information then.
If they don't supply a debugging package, you can help by asking the
vendor to do so.
Lisp backtrace follows:
This backtrace is unfortunately of no help; it essentially says an
internal pointer escaped to Lisp level, an event which is normally
fatal. But it doesn't help at all to help us diagnose why.
Load-Path Lisp Shadows:
----------------------
[...]
/usr/share/xemacs21/site-lisp/debian-startup
/usr/share/emacs/site-lisp/debian-startup
/etc/emacs/site-start
/usr/share/xemacs21/site-packages/lisp/site-start
This last is very bad. Emacs byte-code and XEmacs byte-code are
incompatible, and any attempt to share them is likely to crash one or
both Emacsen. Please report this to the vendor as a possible bug.
(They may know what they're doing, but we can't possibly be sure they
do.)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta