From xemacs-m  Wed Sep 10 11:37:17 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id LAA21939
	for <xemacs-beta@xemacs.org>; Wed, 10 Sep 1997 11:37:15 -0500 (CDT)
Received: (from steve@localhost)
	by altair.xemacs.org (8.8.7/8.8.7) id JAA07803;
	Wed, 10 Sep 1997 09:42:29 -0700
Mail-Copies-To: never
To: xemacs-beta@xemacs.org
Subject: Re: xemacs not dying on logout
References: <b9u4t7wuvlm.fsf@fjo.nada.kth.se> <5v5f2u$h9u@ssbunews.ih.lucent.com> <b9usovdk0k2.fsf@fjo.nada.kth.se> <byk9gp1npd.fsf@midget.math.ethz.ch>
X-Face: `'%\i;ySOu]g?NlziJSk_$&@]KP`}~PEQPjZ5;nxSaDW_o$4+4%Ab]%Ifw3ZR;7TIT3,O,'
 @2{L;]ox6kc;$_5kU'n**9vFg-]eV~GbxSVCx|(s%uR[],*:^WKmC`B}(;|k9/m]gwt?&`t;^rfCJg
 khHH>pP1W\)xM0U@!FNDD72{3fDP$PkBhx^7Z?-WxH6DbFN:QOnT`llzW}VGdYv;n9lzljQvKTIBhQ
 YuV
X-Attribution: sb
From: SL Baur <steve@xemacs.org>
In-Reply-To: Jan Vroonhof's message of "10 Sep 1997 12:13:18 +0200"
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Date: 10 Sep 1997 09:42:28 -0700
Message-ID: <m2n2llw26j.fsf@altair.xemacs.org>
Lines: 53
X-Mailer: Gnus v5.4.65/XEmacs 20.3(beta20) - "Tirana"

Jan Vroonhof <vroonhof@math.ethz.ch> writes:

> fjo@nada.kth.se (Fredrik Jnsson) writes:
>> I've sent in a complete bug report. I'll just post the backtrace as well,
>> if someone is interested.

Presumably this is from a thread in comp.emacs.xemacs.

> This does look interesting.

>> #13 <signal handler called>
>> #12 0x63c64 in fatal_error_signal (sig=13) at emacs.c:195

> So XEmacs DOES get the signal but in the "wrong" signal handler (the
> XIO version is much cleaner).

>> #11 0x656c0 in shut_down_emacs (sig=13, stuff=1344552964) at emacs.c:1914

> and it is shutting down. Hooray!

>> #10 0xa13f8 in Fdo_auto_save (no_message=1344552984, current_only=1344552964)
>> at fileio.c:4306

> This is seems ok...

>> #9  0xef1d0 in check_quit () at signal.c:506

> But we go down hill from here...

Very quickly.  In this case, calling check_quit is not the right thing 
to do.

>> #5  0xef369120 in XCheckIfEvent ()

> It tries to  do X things....

> So somehow we should prevent XEmacs from calling check_quit () when we
> ARE quitting.

Something like that, yes.


check_quit (void)
{
  /* dont_check_for_quit is set in two circumstances:

     (1) when we are in the process of changing the window
     configuration.  The frame might be in an inconsistent state,
     which will cause assertion failures if we check for QUIT.

     (2) when we are reading events, and want to read the C-g
     as an event.  The normal check for quit will discard the C-g,
     which would be bad.

