[jam@athene jam]$
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(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/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:
princ("misc-user misc-user misc-user misc-user misc-user misc-user misc-user
misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user
misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user
misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user
misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user
misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user
misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user
misc-user misc-user misc-user up M-! C-g ! RET M-: ( e m a c s - v e r TAB BS s i o n )
RET button1 button1up C-x C-x 0 C-x 0 button1 button1up misc-user C-h l")
#<compiled-function #<subr
[3]+ Segmentation fault (core dumped) /usr/bin/xemacs -q
-=-=-=-=-=-=-=-=-=-=-=
[jam@athene jam]$ gdb /usr/bin/xemacs core
GDB is free software and you are welcome to distribute copies of it
under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.16 (i586-unknown-linux), Copyright 1996 Free Software Foundation, Inc...
(no debugging symbols found)...
Core was generated by `/usr/bin/xemacs -q'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/X11R6/lib/libXaw.so.6.1...
(no debugging symbols found)...done.
Reading symbols from /usr/lib/libtiff.so.3.4.28...
(no debugging symbols found)...done.
Reading symbols from /usr/lib/libpng.so.2.1.0.2...
(no debugging symbols found)...done.
Reading symbols from /usr/lib/libjpeg.so.6.0.1...
(no debugging symbols found)...done.
Reading symbols from /usr/lib/libz.so.1.0.4...(no debugging symbols found)...
done.
Reading symbols from /usr/X11R6/lib/libXpm.so.4.9...
(no debugging symbols found)...done.
Reading symbols from /usr/X11R6/lib/libXmu.so.6.0...
(no debugging symbols found)...done.
Reading symbols from /usr/X11R6/lib/libXt.so.6.0...
(no debugging symbols found)...done.
Reading symbols from /usr/X11R6/lib/libXext.so.6.3...
(no debugging symbols found)...done.
Reading symbols from /usr/X11R6/lib/libX11.so.6.1...
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)...done.
Reading symbols from /usr/X11R6/lib/libSM.so.6.0...
(no debugging symbols found)...done.
Reading symbols from /usr/X11R6/lib/libICE.so.6.3...
(no debugging symbols found)...done.
Reading symbols from /lib/libdl.so.1.7.14...(no debugging symbols found)...
done.
Reading symbols from /usr/lib/libdb.so.2.0.0...(no debugging symbols found)...
done.
Reading symbols from /usr/lib/libgdbm.so.2.0.0...
(no debugging symbols found)...done.
Reading symbols from /usr/lib/libgpm.so.1.10...(no debugging symbols found)...
done.
Reading symbols from /usr/lib/libncurses.so.3.0...
(no debugging symbols found)...done.
Reading symbols from /lib/libm.so.5.0.6...(no debugging symbols found)...done.
Reading symbols from /lib/libc.so.5.3.12...(no debugging symbols found)...done.
Reading symbols from /lib/ld-linux.so.1...(no debugging symbols found)...done.
(gdb) where
#0 0x810a8b4 in write_c_string ()
(gdb) quit
[jam@athene jam]$
-=-=-=-=-=-=
M-x describe-installation
uname -a: Linux
athene.jamux.com 2.0.35 #1 Wed Jul 15 08:51:05 EDT 1998 i486 unknown
./configure '--cflags=-m486 -O2 -fno-strength-reduce -fno-caller-saves
-fomit-frame-pointer' '--debug=yes' '--gung-ho'
'--with-sound=no' '--with-mule=no' '--use-union-type=yes'
'--lockdir=/var/lock/xemacs' '--prefix=/usr'
XEmacs 21.0 "Poitou" configured for `i486-pc-linux'.
Where should the build process find the source code? /home/jamsrc/xemacs-21.0-b57
What installation prefix should install use? /usr
What operating system and machine description files should XEmacs use?
`s/linux.h' and `m/intel386.h'
What compiler should XEmacs be built with? gcc -m486 -O2
-fno-strength-reduce -fno-caller-saves -fomit-frame-pointer
Should XEmacs use the GNU version of malloc? yes
Should XEmacs use the relocating allocator for buffers? yes
What window system should XEmacs use? x11
Where do we find X Windows header files? /usr/X11R6/include
Where do we find X Windows libraries? /usr/X11R6/lib
Compiling in support for XAUTH.
Compiling in support for XPM images.
Compiling in support for PNG image handling.
Compiling in support for (builtin) GIF image handling.
Compiling in support for JPEG image handling.
Compiling in support for TIFF image handling.
Compiling in support for X-Face message headers.
Compiling in support for Berkeley DB.
Compiling in support for GNU DBM.
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Compiling in support for proper session-management.
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena dialog boxes.
Compiling in DLL support.
movemail will use "dot-locking" for locking mail spool files.
Using the union type for Lisp_Objects.
Using Lisp_Objects with minimal tagbits.
Using indexed lrecord implementation.
Compiling in extra code for debugging.
Compiling in code for checking XEmacs memory usage.
jam