[prev in list] [next in list] [prev in thread] [next in thread]
List: freedesktop-xorg
Subject: =?utf-8?B?UmU6IElzIHRoaXMgaXNzdWUgcmVsYXRlZCB3aXRoIHRoZSBidWcgMjAwNDggLCAxNzkyMyBvciA3MTMzOA==?=
From: "Subrata Dasgupta" <subrata_usha () rediffmail ! com>
Date: 2017-08-04 5:55:15
Message-ID: 1501787338.S.5730.15632.f5-224-143.1501826115.22577 () webmail ! rediffmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Ajax,
Why every time XErrorEvent.serial = 2422603788. Does not it mean application is \
facing problem only after a certain number of requests has been made?? For a huge X \
application this should not be a coincidence. Most importantly this behavior seems to \
be related with the bug 71338. When I checked my libxcb.so and libX11.so it seems 4 \
functions proposed for the fix for 71338(xcb_send_request64, xcb_discard_reply64, \
xcb_wait_for_reply64, xcb_poll_for_reply64) are present within the libxcb.so but \
libX11 do not use the function xcb_send_request64 or xcb_discard_reply64 within it. \
Why this is so ?? Is both fixes properly merged ??
If application is doing something wrong before XIOError, then server should throw \
error before closing the connection, but there is no other protocol error or warning \
event before this XIOError.
Can you please provide where from I get information about the error_code, \
request_code and minor_codes of XErrorEvent structure because I want to understand \
the meaning of the following codes.
XErrorEvent.error_code = 84
XErrorEvent.request_code = 131
XErrorEvent.minor_code = 4
Please help..
Thanks
Subrata
On Fri, 04 Aug 2017 00:38:58 +0530 Adam Jackson wrote
> On Thu, 2017-08-03 at 18:26 +0000, Subrata Dasgupta wrote:
> Hi All,
>
> I have a 32 bit C++ X application running on Linux. Recently
> frequently I am getting strange XIOError event ,below is the stack
> trace. It seems while we get that error application is doing nothing.
> And when I have checked the values within XErrorEvent structure every
> time they are same. Below is data within XErrorEvent structure.
>
> XErrorEvent.type = 604801882
> XErrorEvent.resourceid = 3255051332
> XErrorEvent.serial = 2422603788
> XErrorEvent.error_code = 84
> XErrorEvent.request_code = 131
> XErrorEvent.minor_code = 4
This error can't be real, in the sense that it's almost certainly not
something the server actually sent. 'resourceid' in hex there is
0xC2042444, which isn't a legal value for the client application to
ever see (three most significant bits ought to be zero, and aren't).
But more importantly...
> #11 0xf73..... in _XIOError () from /lib/libX11.so.6
> #12 0xf73..... in _XEventsQueued () from /lib/libX11.so.6
> #13 0xf73..... in XEventsQueued () from /lib/libX11.so.6
> #14 0xf74..... in _XtWaitForSomething () from /lib/libXt.so.6
> #15 0xf74..... in XtAppProcessEvent () from /lib/libXt.so.6
An I/O error indicates that the connection has _closed_, not that a
protocol error happened. What are you doing to provoke the server into
closing your connection?
- ajax
_______________________________________________
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
[Attachment #5 (unknown)]
Hi Ajax,<br />
Why every time XErrorEvent.serial = 2422603788. Does not it mean application is \
facing problem only after a certain number of requests has been made?? For a huge X \
application this should not be a coincidence. Most importantly this behavior seems to \
be related with the bug 71338. When I checked my libxcb.so and libX11.so it seems 4 \
functions proposed for the fix for 71338(xcb_send_request64, xcb_discard_reply64, \
xcb_wait_for_reply64, xcb_poll_for_reply64) are present within the libxcb.so but \
libX11 do not use the function xcb_send_request64 or xcb_discard_reply64 within it. \
Why this is so ?? Is both fixes properly merged ??<br /> <br />
If application is doing something wrong before XIOError, then server should throw \
error before closing the connection, but there is no other protocol error or warning \
event before this XIOError. <br /> <br />
Can you please provide where from I get information about the error_code, \
request_code and minor_codes of XErrorEvent structure because I want to understand \
the meaning of the following codes. <br /> <br />
XErrorEvent.error_code = 84<br />
XErrorEvent.request_code = 131 <br />
XErrorEvent.minor_code = 4<br />
<br />
Please help..<br />
<br />
Thanks<br />
Subrata<br />
<br />
<br />
On Fri, 04 Aug 2017 00:38:58 +0530 Adam Jackson <ajax@nwnk.net> wrote<br />
> On Thu, 2017-08-03 at 18:26 +0000, Subrata Dasgupta wrote:<br />
<br />
> Hi All,<br />
<br />
> <br />
<br />
> I have a 32 bit C++ X application running on Linux. Recently<br />
<br />
> frequently I am getting strange XIOError event ,below is the stack<br />
<br />
> trace. It seems while we get that error application is doing nothing.<br />
<br />
> And when I have checked the values within XErrorEvent structure every<br />
<br />
> time they are same. Below is data within XErrorEvent structure.<br />
<br />
> <br />
<br />
> XErrorEvent.type = 604801882 <br />
<br />
> XErrorEvent.resourceid = 3255051332<br />
<br />
> XErrorEvent.serial = 2422603788<br />
<br />
> XErrorEvent.error_code = 84<br />
<br />
> XErrorEvent.request_code = 131 <br />
<br />
> XErrorEvent.minor_code = 4<br />
<br />
<br />
<br />
This error can't be real, in the sense that it's almost certainly not<br />
<br />
something the server actually sent. 'resourceid' in hex there is<br />
<br />
0xC2042444, which isn't a legal value for the client application to<br />
<br />
ever see (three most significant bits ought to be zero, and aren't).<br />
<br />
<br />
<br />
But more importantly...<br />
<br />
<br />
<br />
> #11 0xf73..... in _XIOError () from /lib/libX11.so.6<br />
<br />
> #12 0xf73..... in _XEventsQueued () from /lib/libX11.so.6<br />
<br />
> #13 0xf73..... in XEventsQueued () from /lib/libX11.so.6<br />
<br />
> #14 0xf74..... in _XtWaitForSomething () from /lib/libXt.so.6<br />
<br />
> #15 0xf74..... in XtAppProcessEvent () from /lib/libXt.so.6<br />
<br />
<br />
<br />
An I/O error indicates that the connection has _closed_, not that a<br />
<br />
protocol error happened. What are you doing to provoke the server into<br />
<br />
closing your connection?<br />
<br />
<br />
<br />
- ajax<br />
<br />
_______________________________________________<br />
<br />
xorg@lists.x.org: X.Org support<br />
<br />
Archives: http://lists.freedesktop.org/archives/xorg<br />
<br />
Info: https://lists.x.org/mailman/listinfo/xorg<br />
<br />
Your subscription address: %(user_address)s<br />
<br>
[Attachment #6 (text/plain)]
_______________________________________________
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic