GNU bug report logs - #16676
24.3.50; Repeated but random hang

Previous Next

Full log

View this message in rfc822 format

From: "Jan D." <jan.h.d <at> swipnet.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Lars Ingebrigtsen <larsi <at> gnus.org>, "16676 <at> debbugs.gnu.org" <16676 <at> debbugs.gnu.org>
Subject: bug#16676: 24.3.50; Repeated but random hang
Date: Sat, 8 Feb 2014 17:40:21 +0100

Hi.

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

>> From: Lars Ingebrigtsen <larsi <at> gnus.org>
>> Cc: 16676 <at> debbugs.gnu.org
>> Date: Sat, 08 Feb 2014 02:23:50 -0800
>> 
>> Eli Zaretskii <eliz <at> 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. 

Previous Next

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