Re: Crash with xemacs 21.4.4
[sorry to resurrect this, but I have some more info]
Darryl Okahata writes:
Andy Piper <andyp(a)bea.com> wrote:
> Right, but which Motif call. Maybe we could just not make the call - sure
> we might get a leak but doesn't seem so bad for delete_device()
I'm not sure it's that simple, as the "offending function" is
XtDestroyWidget(). I've attached a purify fragment that describes
what's happening. Two things to note, though:
1. Purify stack traces are inverted. Most-recently-called functions are
at the top.
2. This is for XEmacs 21.4.4. Line numbers might be occasionally off,
as I was trying to tweak the code to further characterize this bug.
Basically, all of the problems are being caused by internal Motif code,
deep in the bowels.
I'm also seeing this, but I'm not using the graphical progress
widget. What I do is:
C-x C-f ~/test.c
(make-frame-on-display "rpluim-1:0") [this is physically a different
machine and screen]
C-x C-c [on the new frame. doing it on the old frame works fine]
This gives:
#0 0xfec9a118 in _libc_kill () from /usr/lib/libc.so.1
#1 0x77f48 in fatal_error_signal (sig=11)
at /codes/rpluim/xemacs-21.4/src/emacs.c:539
#2 <signal handler called>
#3 0xfee929f4 in XFindContext () from /usr/openwin/lib/libX11.so.4
#4 0xfee92930 in XFindContext () from /usr/openwin/lib/libX11.so.4
#5 0xff297e54 in DisplayDestroy () from /usr/dt/lib/libXm.so.4
#6 0xfefbece0 in XtCallCallbackList () from /usr/openwin/lib/libXt.so.4
#7 0xfefc486c in XtPhase2Destroy () from /usr/openwin/lib/libXt.so.4
#8 0xfefc45d0 in _XtDoPhase2Destroy () from /usr/openwin/lib/libXt.so.4
#9 0xfefc43b4 in XtDestroyWidget () from /usr/openwin/lib/libXt.so.4
#10 0x15cf9c in x_delete_device (d=0x523f00)
This is on Solaris 2.7, using 21.4.5. I'm going to download OpenMotif
and see if that helps, since this points more towards Motif than
XEmacs.
Robert
--