Thank you for reporting this problem.
I'm sorry that nobody has picked up on it yet; looks like we're
shorthanded at the moment. I'm reposting in such a way that it will
be picked up by the issue tracker at
. You can look it up (it
will be issue367 or so) and add yourself to the "nosy list", which
will help you track progress on the issue.
Since the application actually crashed, it would be very helpful if
you are able to reproduce the crash and provide a C stack backtrace
using gdb or other debugger. You may have a core file somewhere (in
your home directory or perhaps in a special place provided by the OS).
If not, it is not unreasonable to run XEmacs under the debugger all
the time; it only uses a small fraction of extra memory and is no
slower. Then you are prepared to get a stack trace if it crashes
XEmacs-Beta mailing list