[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#16676: 24.3.50; Repeated but random hang
From: |
Jan D. |
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@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.
- 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. <=
- 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, 2014/02/08