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

Previous Next

Full log

View this message in rfc822 format

From: Jan Djärv <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
Subject: bug#16676: 24.3.50; Repeated but random hang
Date: Sat, 8 Feb 2014 19:55:11 +0100

Hi.

8 feb 2014 kl. 18:47 skrev Eli Zaretskii <eliz <at> gnu.org>:

>> From: "Jan D." <jan.h.d <at> swipnet.se>
>> Date: Sat, 8 Feb 2014 17:40:21 +0100
>> Cc: Lars Ingebrigtsen <larsi <at> gnus.org>,
>> "16676 <at> debbugs.gnu.org" <16676 <at> debbugs.gnu.org>
>> 
>> 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.
> 
> Is it wise to issue further X calls in this situation?  Maybe we
> should skip X calls when we delete the frame as result of such
> problems.

No, you can not do any calls.  In fact, if the I/O error handler returns, Xlib does exit.
That is why x_connection_closed does a longjump (throws an error).

	Jan D.

Previous Next

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