From: Dan Nicolaescu <dann@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: Dmitry Antipov <dmantipov@yandex.ru>, 15025@debbugs.gnu.org
Subject: bug#15025: emacs --daemon stuck in infinite loop
Date: Fri, 09 Aug 2013 09:25:19 -0400 [thread overview]
Message-ID: <yxq8v0b3sjk.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <5204B28B.2060505@gmx.at> (martin rudalics's message of "Fri, 09 Aug 2013 11:12:43 +0200")
martin rudalics <rudalics@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.
next prev parent reply other threads:[~2013-08-09 13:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 12:36 bug#15025: emacs --daemon stuck in infinite loop Dan Nicolaescu
2013-08-06 23:55 ` Glenn Morris
2013-08-07 2:13 ` Dmitry Antipov
2013-08-09 1:23 ` Dan Nicolaescu
2013-08-09 2:34 ` Dmitry Antipov
2013-08-09 9:12 ` martin rudalics
2013-08-09 13:25 ` Dan Nicolaescu [this message]
2013-08-09 15:00 ` Dmitry Antipov
2013-08-09 19:14 ` Dan Nicolaescu
2013-08-09 20:34 ` martin rudalics
2013-08-09 21:54 ` Dan Nicolaescu
2013-08-12 8:10 ` Dmitry Antipov
2013-08-13 14:41 ` Dan Nicolaescu
2013-08-14 17:43 ` Dmitry Antipov
2013-08-15 15:40 ` Dmitry Antipov
2013-08-16 18:36 ` Dan Nicolaescu
2013-08-09 17:09 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yxq8v0b3sjk.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=15025@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).