Hey, guys, I don't understood why my xemacs complain like this. I appreciate if you have some idea.
before I did some configure to display and input chinese, my both and emacs xemacs work happy on my redhat 8.0. I am not an expert in linux and I am not sure have me touched anything required fo xemacs. now whenever I try to run xemacs, it come out in this way:

[root@localhost fubin]# xemacs &
[2] 16942
[1] Segmentation fault xemacs
[root@localhost fubin]# Warning: Color name "Gray90" is not defined
Warning: Color name "Gray40" is not defined
Warning: Color name "Gray80" is not defined
Warning: Color name "Black" is not defined
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string "-*-gothic-medium-r-normal--14-120-75-75-c-*-*-*" to type FontSet
Warning: Color name "Gray30" is not defined
Warning: Color name "Blue" is not defined
Warning: Color name "Red" is not defined
Warning: Color name "Maroon" is not defined
Warning: Color name "ForestGreen" is not defined

Fatal error (11).

Your files have been auto-saved.
Use `M-x recover-session' to recover them.

If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting `Send Bug Report'
from the help menu.
As a last resort send ordinary email to `crashes@xemacs.org'.
*MAKE SURE* to include the information in the command
M-x describe-installation.

If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type

gdb /usr/bin/xemacs core

then type `where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB. A similar procedure should work for all of
these. Ask your system administrator if you need more help.)

Lisp backtrace follows:

# bind (frame-being-created)
make-frame(nil #<x-device on ":0.0" 0x7b2>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (condition-case ... . ((t (byte-code " ??" ... 1))))
# bind (error-data)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)

[2]+ Segmentation fault xemacs
[root@localhost fubin]# ps
PID TTY TIME CMD
4833 pts/0 00:00:00 su
4836 pts/0 00:00:00 bash
16943 pts/0 00:00:00 ps
[root@localhost fubin]#


thanks for your time.