xemacs-21.1.14

Mr. Crashes: First of all, thanks for taking the time to look. I'm having problems running xemacs after configure/make/make install. Running it fails immediately with Fatal error (11), then a seg fault. I've included the following information as attachment: C stacktrace 'ldconfig -v' output I've inlined the following info: compilation flags machine description 'uname -a' output execution output I compile it using a shell script and call this function: compile() { cd $DIR_NAME ./configure --prefix=/tools/pkg make } The machine is a dual-processor Athlon running on the relatively new Tyan MP S2460 motherboard. However, looking at the stacktrace, I don't think this is related. I have 1.5 GB of RAM and 40 GB of disk space in a RAID-1 configuration. I've also attached the output of <ldconfig -v>. Let me know if you need any more info to help me debug this problem. * * * gemini [~/proj/pkg/src/xemacs] $ uname -a Linux gemini 2.4.10-64GB-SMP #1 SMP Fri Sep 28 17:26:36 GMT 2001 i686 unknown * * * gemini [~] $ xemacs 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&#39;. *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 /tools/pkg/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" 0x1a13>) 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