all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	"16676@debbugs.gnu.org" <16676@debbugs.gnu.org>
Subject: bug#16676: 24.3.50; Repeated but random hang
Date: Sat, 8 Feb 2014 17:40:21 +0100	[thread overview]
Message-ID: <26DA7E1C-7874-41A1-B1CE-8E500EEA22CF@swipnet.se> (raw)
In-Reply-To: <83lhxlx47c.fsf@gnu.org>

Hi.

8 feb 2014 kl. 11:56 skrev Eli Zaretskii <eliz@gnu.org>:

>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Cc: 16676@debbugs.gnu.org
>> Date: Sat, 08 Feb 2014 02:23:50 -0800
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>>> Xlib obviously thinks otherwise, the error message in the backtrace is
>>> very clear.
>> 
>> Well, might not something have scribbled something somewhere to make X
>> believe the window is no longer viable?
> 
> I'm not an expert on this, so I don't know.  Jan, can you comment,
> please?

The io error handler is only called for fatal errors.  Any system call related to io in Xlib that fails
triggers a call to the error handler.  Xlib can not recover from this, so the connection is lost.
If something writes garbage into Xlibs data, anything can happen.

    Jan D. 




  reply	other threads:[~2014-02-08 16:40 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
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. [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=26DA7E1C-7874-41A1-B1CE-8E500EEA22CF@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.