xemacs on slackware
I am trying to install xemacs on a slackware linux system. xemacs
compiles fine, but when I run it I get the following output:
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(a)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/src/xemacs-21.1.14/src/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" 0x1a12>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (unwind-protect ...)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
Segmentation fault
I do not get this error when running xemacs at console, only in X windows.
This happens with every version in the 'stable' branch. I haven't tried
any other branch. I *would* include a C trace, but the "core" file
mentioned above does not exist. I would send you the information from
M-x describe-installation, but I can't get far enough into xemacs to
execute the command. I know this is very little information, but I am
unsure what else to send you. I would be happy to provide any further
information that could help you to help me understand what I am doing wrong.
Thank you,
Paul D. Lathrop