[Bug: 21.5-b28]

[Stephen J. Turnbull]

Søren Feodor Nielsen writes:

 > XEmacs crashed for me when I was trying to change the font; below is
 > the output.

It would be very helpful if you can give us an exact sequence of
keystrokes and/or mouse gestures to reach the crash starting from
"xemacs -vanilla" on the command line.  Without that we may be unable
to reproduce the crash.

 > I had little luck in obtaining the "C stack backtrace" following
 > the directions below.

We really need to get a C backtrace to debug the problem.  A crash is
*never* the fault of Lisp code; Lisp code cannot crash. ;-) However,
the C implementation of Lisp primitives can.

I believe that Red Hat-derived distros such as Fedora have a special
place they put core files, and they are named something like
"core.$$12345" or "xemacs.$$12345" where the "12345" is the process ID
of the XEmacs that crashed.  If you can't find that core, but can
reproduce the crash, you can do "gdb `which xemacs` | tee -a
~/gdb.out", then type "run" to gdb, reproduce the crash, and finally
"bt".  The "tee" command allows you to capture the output in the file
~/gdb.out which you can just attach to your post.