Re: [crash] assertion failed, file specifier.c, line 2451, abort()

Some time ago, Greg Klanderman wrote... |+ | | I see the same backtrace on the second and subsequent times I run | ediff-buffers in b36, when I have my focus-follows-mouse fixes (which | don't quite work yet) applied. Backing them out avoids the assert | fail, but I still get the odd behavior that on the second and | subsequent runs of ediff-buffers, a floating minibuffer-only frame is | created. Any ideas what's up with that? This is with -q, btw. |- Greg, If you have steady reproduction, please try this. There is a GC problem which is fixed by this patch; I only wanted to be sure that all Karl's crashes are really caused by this. I was not able to reproduce it by normal means. Kirill 1998-04-24 Kirill M. Katsnelson <kkm(a)kis.ru&gt; * frame.c (Fmake_frame): GC-protect new frame immediately upon creation. Index: src/frame.c =================================================================== RCS file: /var/cvsroot/ntxemacs/src/frame.c,v retrieving revision 1.4 diff --unified=2 -r1.4 frame.c --- src/frame.c 1998/04/05 13:16:54 1.4 +++ src/frame.c 1998/04/23 21:57:46 ＠＠ -417,4 +417,5 ＠＠ f = allocate_frame_core (device); + XSETFRAME (frame, f); specbind (Qframe_being_created, name); ＠＠ -446,5 +447,4 ＠＠ signal_simple_error ("Invalid value for `minibuffer'", minibuf); - XSETFRAME (frame, f); update_frame_window_mirror (f);