Thank you for your report. Unfortunately, without the C stack
backtrace, there is no hope of debugging a crash or hang. If you wish
to help debug this problem, you could run XEmacs under gdb and the
next time the hang occurs, use C-z in the debugger to interrupt
XEmacs, then use the bt command to get a stack trace to determine what
code is looping or blocked.
I run XEmacs in this way all the time; it does not affect XEmacs's
performance in any way (except that if you run it without a GUI
window, the debugger will intercept certain keystrokes, especially
C-z; this happens even in a remote terminal window, which can be quite
disconcerting and disruptive to your work if you're far from the
terminal where gdb is running). Of course you also have gdb loaded in
memory all the time, but gdb is much smaller than XEmacs. It doesn't
affect the system performance negatively unless you're really really
tight on RAM or VM.
Also, you are using a very old version of XEmacs; the current version
of the 21.4 series is 21.4.21. Many bugs have been fixed in the
intervening releases, and we strongly recommend upgrading to the most
recent version.
Jakob Heitz writes:
I ran ediff on two buffers and it hung. Then I killed it.
It's done this several times before.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta