From xemacs-m  Wed Jan 22 21:43:18 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
          by xemacs.org (8.8.4/8.8.4) with ESMTP
	  id VAA12776 for <xemacs-beta@xemacs.org>; Wed, 22 Jan 1997 21:43:16 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQbzri20678; Wed, 22 Jan 1997 22:43:09 -0500 (EST)
Date: Wed, 22 Jan 1997 22:43:09 -0500 (EST)
Message-Id: <QQbzri20678.199701230343@crystal.WonderWorks.COM>
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Re: 19.15b90: another crash in Fkill_emacs
In-Reply-To: <rvenfdjhrc.fsf@sdnp5.ucsd.edu>
References: <QQbzqz18666.199701230119@crystal.WonderWorks.COM>
	<rvenfdjhrc.fsf@sdnp5.ucsd.edu>

David Moore writes:
 > Kyle Jones <kyle_jones@wonderworks.com> writes:
 > 
 > > #6  0x90dd5 in delete_frame_internal (f=0x966000, force=271941636, called_from_delete_device=1, from_io_error=0) at frame.c:1437
 > > #7  0x30ed6 in delete_device_internal (d=0x3dd100, force=1, called_from_delete_console=1, from_io_error=0) at device.c:774
 > 
 > 	I note that delete_device_internal calls delete_frame_internal
 > with force = 1, so something seems to be messing with the stack.
 > 
 > 	Looking in delete_device_internal, I wonder if you have frames
 > w/o minibuffers?  Hmm, the particular case that is failing is related to
 > frames with the popup property set.  Are you still running with
 > balloon-help enabled?

I don't use minibuffer-less frames but I am still running with
balloon-help enabled.

