Hello,
I am using a desk top and run our project environment setting
for cpu design project at Sunnyvale.
In the last several weeks, when I type xemacs, it will
print out the following messages and then pop up a xemacs GUI.
But when I move my cursor to the GUI, it will "beep" and start
printing the similar message on the screen.
Help! x_get_gc got a bogus fg value! fg = #<INTERNAL EMACS BUG (symfwd
13) 0x24d2a4>
Help! x_get_gc got a bogus fg value! fg = #<INTERNAL EMACS BUG (symfwd
13) 0x24d2a4>
Help! x_get_gc got a bogus fg value! fg = #<INTERNAL EMACS BUG (symfwd
13) 0x24d2a4>
H
So someone suggests me to use "xemacs -nw". BUT while I was
running "xemacs -nw", I closed the window without using
CTrl-x-c to exit emacs.
Now I am having the following problem.
=================================================================
Fatal error: assertion failed, file
/set/ipe/sb2/xemacs-19.14-release/editor/src/glyphs-x.c, line 2537, abort()
Fatal error (6).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
Please report this bug to the address `crashes(a)xemacs.org'.
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 XEmacs, or maybe in your home
directory), and type
gdb /usr/dist/share/xemacs,v19.14/5bin.sun4/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.)
Abort
=================================================================
I could not find any "core" file from xemacs. Please let me
know what should I do to resolve these two problems.
Thanks.
Sincerely,
Chu-Chih