GNU bug report logs - #15025
emacs --daemon stuck in infinite loop

Previous Next

Package: emacs;

Reported by: Dan Nicolaescu <dann <at> gnu.org>

Date: Mon, 5 Aug 2013 12:37:01 UTC

Severity: important

Fixed in version 24.4

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Dan Nicolaescu <dann <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: Dmitry Antipov <dmantipov <at> yandex.ru>, 15025 <at> debbugs.gnu.org
Subject: bug#15025: emacs --daemon stuck in infinite loop
Date: Fri, 09 Aug 2013 09:25:19 -0400
martin rudalics <rudalics <at> gmx.at> writes:

>>> next_frame has that loop "while (passed < 2)" where emacs gets stuck,
>>> but prev_frame does not.  Any idea what can it make it get stuck there?
>>
>> Hm... strange values (dead frame?) in Vframe_list may be a reason.
>
> IIUC failing to increment passed can happen only if the frame next_frame
> got called with is not on Vframe_list.  We could try asserting that it is.

That gives the idea of killing multiple emacsclients at the same time...

This looks reproducible:

Xnest :1
xterm -display :1
in that xterm:
emacs -Q --deamon

from the :0 display create 2 more xterms in Xnest:
xterm -display :1
xterm -display :1

and in each of the do 
emacsclient -t 
C-z


in another xterm on :0 do:
emacsclient -t 
C-z

at this point we should have 3 suspended emacsclients, 2 in Xnest, one
in the main display.

Kill Xnest

Now emacs is stuck. VframeList looks like it's empty.




This bug report was last modified 11 years and 281 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.