Andy Piper <andy(a)xemacs.org> wrote:
Fixed
Not on my system, unfortunately. The behavior has changed in that now
just after sending the message XEmacs freezes. Killing it shows the
following:
LUCY:/usr/local/src/xemacs-21.2$src/xemacs.exe &
[1] 1532
LUCY:/usr/local/src/xemacs-21.2$kill 1532
Lisp backtrace follows:/usr/local/src/xemacs-21.2
$
# bind (inhibit-quit)
# (condition-case ... . error)
# (catch top-level ...)
[1]+ Terminated src/xemacs.exe
LUCY:/usr/local/src/xemacs-21.2$
(I've cvs updated this morning - May 9, around 11:00 EST.)
At 09:36 AM 5/6/00 -0400, Dmitry Yaitskov wrote:
>Andy Piper <andy.piper(a)bea.com> wrote:
>
>> This should fix. I still need reproducible cases for the others, but I've
>> only had 2 hours sleep so I'm off to bed ....
>>
>> andy
>>
>> 2000-05-05 Andy Piper <andy(a)xemacs.org>
>>
>> * window.c (window_unmap_subwindows_cache_mapper): remove the dead
>> instance from the frame cache also since GC may catch up too late
>> to make frame deletion sane.
>>
>>
>>
>> --------------------------------------------------------------
>> Dr Andy Piper
>> Principal Consultant, BEA Systems Ltd
>
>FWIW, with this change I still get the crash (on my system, it is
>consistent) after sending a mail from gnus. The XEmacs screen goes
>blank and apparently it is the scratch buffer (instead of the usual
>group), switching to the group buffer still shows a blank screen,
>buffer list shows up but selecting anything from it freezes XEmacs.
>
>(This is under cygwin)
>
>--
>Cheers,
>-Dima.
>
>
>
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
--
Cheers,
-Dima.