Hi,
First I compiled XEmacs 21.5 (beta9) with this option:
> --prefix=/usr/local --with-sound=no --with-mule --error-checking=none
and all works great. But then I tried to use the new external widget function
and compiled with:
> --prefix=/usr/local --with-sound=no --with-mule --error-checking=none --external-widget
Since then I get this error message if I close a 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'.
*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/local/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:
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
kill-emacs()
# bind (arg)
save-buffers-kill-emacs()
delete-frame(#<x-frame "emacs" 0xc749> t)
eval((delete-frame #<x-frame "emacs" 0xc749> t))
# (condition-case ... . error)
# (catch top-level ...)
Segmentation fault
-----------------------------------------------------------------------------
Here is my output from M-x describe-installation:
-----------------------------------------------------------------------------
uname -a: Linux frodo 2.4.20-k7 #22 Don Jul 3 21:58:56 GMT+2 2003 i686 unknown
./configure '--prefix=/usr/local' '--with-sound=no' '--with-mule' '--error-checking=none' '--external-widget'
XEmacs 21.5-b9 "brussels sprouts" configured for `i686-pc-linux'.
Compilation / Installation:
Source code location: /usr/local/src/xemacs/xemacs-21.5.9
Installation prefix: /usr/local
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: /opt/gcc-3.2/bin/gcc -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -Wshadow
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Linking with `-z nocombreloc'.
- Consider configuring with --pdump.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Using Lucid menubars.
Using Lucid scrollbars.
Using Motif dialog boxes.
Using Motif native widgets.
TTY:
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Sound:
Databases:
Compiling in support for Berkeley database.
Compiling in support for LDAP.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using Motif to provide XIM support.
Mail:
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Compiling in support for extra debugging code.
-----------------------------------------------------------------------------
But I couldn't find the place where xemacs places the core file. Do I need to
activate the core-file ability before?
If I exec xemacs with gdb this is printed:
...
Starting program: /usr/local/bin/xemacs-21.5-b9
Program exited normally.
...
Why is here no "Segmentation fault"?
Is this a correct list for beta bug reports or is there a better one?
Thanks
Andreas