-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
record extension will cause xgb blocked #16
Comments
Thanks for this. The next step, I think, is to produce an equivalent program with XCB and see what happens there. I basically don't have the time to fix this right now. If you discover a fix, a pull request is welcome. Just make sure that any fixes you make are either in the core |
http://stackoverflow.com/questions/20823894/xcb-record-x11-extension-example |
I write an example in golang
I think the reason for the bug is that the sequence id of the reply sent by the x server is equal to the sequeue id of the previous cookie. add this line to xgb/xgb.go:460
You will know where the problem , I do not know how to fix it. |
@electricface I don't know when or if I'll have time to look at this. Sorry. |
test code:
below is the x11 request and reply captured by wireshark.
https://drive.google.com/file/d/0B9yQfM5tUO9uMXBqUEFUNkNfTk0/edit?usp=sharing
The text was updated successfully, but these errors were encountered: