[Bug: 21.5-b28] Crash when closing xemacs via window manager
Stephen J. Turnbull
stephen at xemacs.org
Fri Aug 8 14:18:35 EDT 2008
Raymond Toy writes:
> ================================================================
> Dear Bug Team!
>
> Here's a 100% repeatable crash for me on Solaris 10. This is from a
> cvs build from 2008-06-01. (Yes, I'm slow to update cvs builds.)
I think we've seen something like this before, I'll check later.
> Run xemacs -vanilla. After the splash screen is displayed, use the
> window manager button to kill the window.
I suspect that the window manager is just destroying the window
without giving XEmacs a chance to do it itself. What window manager
are you using?
Also, if you have two windows open, do you get the X Errors? Do you
get the crash?
> And so on. Then it dumps core. The backtrace says:
>
> #0 0xfe746398 in kill () from /lib/libc.so.1
> #1 0x000c3b68 in fatal_error_signal (sig=10)
> at /apps/public/XEmacs/src/xemacs-21.5-2008-06-01/src/emacs.c:3801
> #2 0xfe74592c in __sighndlr () from /lib/libc.so.1
> #3 0xfe73a870 in call_user_handler () from /lib/libc.so.1
> #4 0x00055854 in malloc_after (val=0x26b8e4, size=2)
> at /apps/public/XEmacs/src/xemacs-21.5-2008-06-01/src/alloc.c:314
> #5 0xfed2666c in XtWidgetToApplicationContext ()
> from /usr/openwin/lib/libXt.so.4
I don't understand why XtWidgetToApplicationContext is calling
`malloc_after', which is a static XEmacs function. Could you try
rebuilding with --with-cflags="--no-thread-jumps --no-crossjumping"
and seeing if the backtrace gives more detail at that point?
More information about the XEmacs-Beta
mailing list