failure report: 21.0.60 dies on Xt error

(I'm not [yet] an xemacs-beta subscriber; please reply directly if needed.) I can readily induce a SEGV failure when disposing of a 2nd frame, usually having been created via hitting the *Info* button in the toolbar. Generally, the circumstance seems to be related to whether the original buffer from which the 2nd was created was "busy", where "busy" means, *very* roughly, that the original buffer had enough text in it that it had extended below the bottom of the visible buffer space; if the original buffer contains a small file which doesn't extend beyond visible bottom, I don't seem to get this error. (I don't explain it, I just report it.) This particular stack trace was caused by having gotten into *Info*, wandering around the Gnus manual for a while, and then hitting the exit toolbar button in *Info*. The attempt to delete the frame fails. "Installation" is after the trace. This is RedHat 5.1, Linux 2.0.34, assorted XFree RPMs 3.3.2.3-18, and Motif 2.0.1. --karl (gdb) r Starting program: /usr/local/bin/xemacs-21.0-b60 Program received signal SIGSEGV, Segmentation fault. 0x40262d2d in XtIsSubclass () (gdb) bt #0 0x40262d2d in XtIsSubclass () #1 0x40263a36 in XtDisplayOfObject () #2 0x400fd135 in unset_current_xic () #3 0x400fb759 in _XmImFreeShellData () #4 0x40115423 in Destroy () #5 0x40259e36 in Phase2Destroy () #6 0x40259c97 in Recursive () #7 0x4025a16a in XtPhase2Destroy () #8 0x4025a249 in _XtDoPhase2Destroy () #9 0x4025a3c7 in XtDestroyWidget () #10 0x8161ae8 in x_delete_frame (f=0x884a590) at frame-x.c:2651 #11 0x80f7d5f in delete_frame_internal (f=0x884a590, force=0, called_from_delete_device=0, from_io_error=0) at frame.c:1530 #12 0x80f7fa3 in Fdelete_frame (frame=142910864, force=137130132) at frame.c:1676 #13 0x80a802e in Feval (form=142350672) at eval.c:3063 #14 0x80a61f5 in condition_case_3 (bodyform=142350672, var=137130132, handlers=142346884) at eval.c:1653 #15 0x80887af in Fbyte_code (bytestr=140636292, vector=142698928, maxdepth=7) at bytecode.c:576 #16 0x80a9296 in funcall_lambda (fun=139917484, nargs=0, arg_vector=0xbfffef60) at eval.c:3597 #17 0x80a87d5 in funcall_recording_as (recorded_as=139917484, nargs=0, args=0xbfffef5c) at eval.c:3214 #18 0x80a96c2 in apply1 (fn=139917484, arg=137130132) at eval.c:3238 #19 0x80897b7 in Fcall_interactively (function=142684932, record_flag=137130132, keys=137130132) at callint.c:397 #20 0x80a85a7 in funcall_recording_as (recorded_as=137202896, nargs=1, args=0xbffff1f4) at eval.c:3193 #21 0x80a88c1 in Ffuncall (nargs=2, args=0xbffff1f4) at eval.c:3238 #22 0x80883e2 in Fbyte_code (bytestr=136643524, vector=136643672, maxdepth=9) at bytecode.c:416 #23 0x80a9296 in funcall_lambda (fun=136643808, nargs=1, arg_vector=0xbffff31c) at eval.c:3597 #24 0x80a87d5 in funcall_recording_as (recorded_as=138027296, nargs=1, args=0xbffff318) at eval.c:3214 #25 0x80a88c1 in Ffuncall (nargs=2, args=0xbffff318) at eval.c:3238 #26 0x808ac1d in Fcall_interactively (function=138027296, record_flag=137130132, keys=137130132) at callint.c:949 #27 0x80a73a3 in Fcommand_execute (cmd=138027296, record=137130132, keys=137130132) at eval.c:2584 #28 0x80d79b6 in execute_command_event (command_builder=0x83ee148, event=142956256) at event-stream.c:4346 #29 0x80d8082 in Fdispatch_event (event=142956256) at event-stream.c:4685 #30 0x80901ac in Fcommand_loop_1 () at cmdloop.c:579 #31 0x809003a in command_loop_1 (dummy=137130132) at cmdloop.c:494 #32 0x80a5f45 in condition_case_1 (handlers=137130244, bfun=0x8090024 <command_loop_1>, barg=137130132, hfun=0x808fc44 <cmd_error>, harg=137130132) at eval.c:1653 #33 0x8090380 in command_loop_2 (dummy=137130132) at cmdloop.c:256 #34 0x80a5d68 in internal_catch (tag=137204840, func=0x809034c <command_loop_2>, arg=137130132, threw=0x0) at eval.c:1328 #35 0x808fe7e in initial_command_loop (load_me=137130132) at cmdloop.c:305 #36 0x80a345d in xemacs_21_0_b60_i686_pc_linux (argc=1, argv=0xbffff758, envp=0xbffff760, restart=0) at emacs.c:1705 #37 0x80a3b19 in main (argc=1, argv=0xbffff758, envp=0xbffff760) at emacs.c:2122 uname -a: Linux beaver.jprc.com 2.0.34 #1 Tue Jul 21 16:49:33 EDT 1998 i686 unkn own ./configure '--with-pop' '--with-mule' '--with-png' '--error-checking=none' XEmacs 21.0-b60 "Poitou60" configured for `i686-pc-linux'. Where should the build process find the source code? /home/karl/src/x/xemac s-21/xemacs-21.0.60 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno- switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11/include Where do we find X Windows libraries? /usr/X11/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using POP for mail access Using Lisp_Objects with minimal tagbits. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage.