[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#16676: 24.3.50; Repeated but random hang
From: |
Jan Djärv |
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@gnu.org>:
>> From: "Jan D." <jan.h.d@swipnet.se>
>> Date: Sat, 8 Feb 2014 17:40:21 +0100
>> Cc: Lars Ingebrigtsen <larsi@gnus.org>,
>> "16676@debbugs.gnu.org" <16676@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.
- bug#16676: 24.3.50; Repeated but random hang, Lars Ingebrigtsen, 2014/02/06
- bug#16676: 24.3.50; Repeated but random hang, Eli Zaretskii, 2014/02/07
- bug#16676: 24.3.50; Repeated but random hang, Dmitry Antipov, 2014/02/07
- bug#16676: 24.3.50; Repeated but random hang, Lars Ingebrigtsen, 2014/02/07
- bug#16676: 24.3.50; Repeated but random hang, Eli Zaretskii, 2014/02/08
- bug#16676: 24.3.50; Repeated but random hang, Lars Ingebrigtsen, 2014/02/08
- bug#16676: 24.3.50; Repeated but random hang, Eli Zaretskii, 2014/02/08
- bug#16676: 24.3.50; Repeated but random hang, Jan D., 2014/02/08
- bug#16676: 24.3.50; Repeated but random hang, Eli Zaretskii, 2014/02/08
- bug#16676: 24.3.50; Repeated but random hang,
Jan Djärv <=