From xemacs-m  Mon Apr 21 18:16:56 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id SAA02349
	for <xemacs-beta@xemacs.org>; Mon, 21 Apr 1997 18:16:54 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQcmhh23838; Mon, 21 Apr 1997 19:16:53 -0400 (EDT)
Date: Mon, 21 Apr 1997 19:16:53 -0400 (EDT)
Message-Id: <QQcmhh23838.199704212316@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Re: Build Success - 20.2b1 - Linux2.0.28, but...
In-Reply-To: <m2d8roggs5.fsf@altair.xemacs.org>
References: <m2iv1hg0w7.fsf@sauna.ton.tut.fi>
	<m2hgh1obrn.fsf@altair.xemacs.org>
	<QQcmcx22856.199704201851@crystal.WonderWorks.COM>
	<m2iv1hsdau.fsf@sauna.ton.tut.fi>
	<QQcmdo26168.199704202313@crystal.WonderWorks.COM>
	<m2ohb8gj2i.fsf@altair.xemacs.org>
	<QQcmha22540.199704212138@crystal.WonderWorks.COM>
	<m2d8roggs5.fsf@altair.xemacs.org>
X-Mailer: VM 6.28 under 20.2 XEmacs Lucid (beta1)
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Steven L Baur writes:
 > You never said, did this crash bear any relationship to the
 > balloon-help ones?

Looks unrelated now.

 > Kyle Jones <kyle_jones@wonderworks.com> writes:
 > 
 > > Anything that can cause the menubar widget state to be fiddled
 > > with can cause a crash if it is called from a menubar :filter
 > > callback.  It probably applies to :selected and :active callbacks
 > > also, but I haven't verified that.
 > 
 > > At the very least this means that Fnext_event/next-event calls
 > > must signal an error if called from within the guts of the menu
 > > code.  A simple semaphore like in_menubar ought to do it, ugly
 > > though it is.
 > 
 > Do you see any straight-forward way of doing this?  The event code
 > does not know when it is calling menubar code.  lwlib was originally
 > written to be independent of application and appears to have many
 > ugly-looking entry points.

I think we can set and unset the flag around calls to
XtCallCallbackList.  It is gross, but rewriting the menubar code
to be able to survive reentrancy is not a project I'm ready to
tackle just now.  Since I've spent time looking at it, I'm
willing to generate a patch for us to try.

