unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Antipov <dmantipov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 16676@debbugs.gnu.org
Subject: bug#16676: 24.3.50; Repeated but random hang
Date: Fri, 07 Feb 2014 12:27:10 +0400	[thread overview]
Message-ID: <52F498DE.6070008@yandex.ru> (raw)
In-Reply-To: <83txcbxtg7.fsf@gnu.org>

On 02/07/2014 11:39 AM, Eli Zaretskii wrote:

> My reading of this is: Emacs was at the end of a redisplay cycle, when
> a call to an X function signaled an error because "Connection lost to
> X server `:0'".  Then Emacs tried to delete the frame on that display,
> which again involves calls to X.

Yes, and I'm just curious why fatal X errors are handled in the same way
as non-fatal (by x_connection_closed). IIUC if X connection is broken
at the socket level, X protocol command may result in undefined behavior.
Manual says that XIfEvent flushes an event queue and waits for an event
matching the predicate; I don't know how the socket connection was broken
exactly, but it was "broken enough" to wait forever.

> Do you know why the connection was lost in the first place?

Shouldn't we try to check errno x_io_error_quitter? Socket-related calls
should set it in case of error.

Dmitry







  reply	other threads:[~2014-02-07  8:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07  0:53 bug#16676: 24.3.50; Repeated but random hang Lars Ingebrigtsen
2014-02-07  7:39 ` Eli Zaretskii
2014-02-07  8:27   ` Dmitry Antipov [this message]
2014-02-08  1:08   ` Lars Ingebrigtsen
2014-02-08  8:48     ` Eli Zaretskii
2014-02-08 10:23       ` Lars Ingebrigtsen
2014-02-08 10:56         ` Eli Zaretskii
2014-02-08 16:40           ` Jan D.
2014-02-08 17:47             ` Eli Zaretskii
2014-02-08 18:55               ` Jan Djärv
2014-11-14 15:37 ` Lars Magne Ingebrigtsen

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=52F498DE.6070008@yandex.ru \
    --to=dmantipov@yandex.ru \
    --cc=16676@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    /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).