aarora at marvell.com
Mon Feb 26 20:05:46 EST 2007
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
Your version of XEmacs was distributed with a PROBLEMS file that may describe
your crash, and with luck a workaround. Please check it first, but do report
the crash anyway. Please report this bug by invoking M-x report-emacs-bug,
or by selecting `Send Bug Report' from the Help menu. If necessary, send
ordinary email to `crashes at xemacs.org'. *MAKE SURE* to include the XEmacs
configuration from M-x describe-installation, or equivalently the file
Installation in the top of the build tree.
*Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely
to be able to analyze the problem. Locate the core file produced as a result
of this crash (often called `core' or `core.<process-id>', and located in
the directory in which you started XEmacs or your home directory), and type
gdb /usr/bin/xemacs core
then type `where' at the debugger prompt. No GDB on your system? You may
have DBX, or XDB, or SDB. (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited'
in case of future recurrance of the crash.
Lisp backtrace follows:
# bind (frame-being-created)
make-frame(nil #<x-device on "msi-pa-2059.marvell.com:1.0" 0xa8f>)
# bind (debugger debug-on-error command-line-args-left)
# (condition-case ... . ((t (byte-code " Â§" ... 1))))
# bind (error-data)
# (condition-case ... . error)
# (catch top-level ...)
 Segmentation fault /usr/bin/xemacs
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the XEmacs-Beta