Nathaniel and Barton found a theoretical situation that would cause this crash
(http://lists.freedesktop.org/archives/xcb/2009-January/004248.html) but it hasn't actually been proven that this situation is happening.
If this situation is happening, it can be detected by
* getting debuginfo packages for libxcb, and
* setting a conditional breakpoint on the line in xcb_generate_id after the
call to xcb_xc_misc_get_xid_range_reply, with condition "range->count == 1".
(It is not necessary to run with --sync.)
If the breakpoint is hit, then the program will crash soon afterwards.
If the BadIDChoice results without hitting the breakpoint, then there is also another bug.
Nathaniel and Barton found a theoretical situation that would cause this crash lists.freedeskt op.org/ archives/ xcb/2009- January/ 004248. html) but it hasn't actually been proven that this situation is happening.
(http://
If this situation is happening, it can be detected by
* getting debuginfo packages for libxcb, and misc_get_ xid_range_ reply, with condition "range->count == 1".
* setting a conditional breakpoint on the line in xcb_generate_id after the
call to xcb_xc_
(It is not necessary to run with --sync.)
If the breakpoint is hit, then the program will crash soon afterwards.
If the BadIDChoice results without hitting the breakpoint, then there is also another bug.