![](https://seccdn.libravatar.org/avatar/e9d4c53421fca81578f71068153aeb80.jpg?s=120&d=mm&r=g)
This is a multi-part message in MIME format. --------------A4844B4DF023E4D39306B867 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I went to use xemacs today, and noticed that I had I tiny problem with it. That problem is that it doesn't work at all. It sounds like it is starting up (I hear the harddrives), the cpu usage goes up, but all that happens is that I get a fatal error message. I am attaching the error message. Any suggestions. Should I just download it from ftp.xemacs.org? Steve Cohen --------------A4844B4DF023E4D39306B867 Content-Type: text/plain; charset=us-ascii; name="xemacs-error.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="xemacs-error.txt" Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. 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 as much configuration information as possible; at the very least what OS and hardware you are running on, and hopefully also what compiler and compiler options the binary was compiled with, what options XEmacs was compiled with, whether you are using a prebuilt binary from ftp.xemacs.org or compiled XEmacs yourself for your system, etc. 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/X11R6/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: --------------A4844B4DF023E4D39306B867-- -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e