Summary: | two more assertion in xcb_xlib_lock | ||
---|---|---|---|
Product: | xorg | Reporter: | Lars Knoll <lars> |
Component: | Lib/Xlib | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | highest | CC: | jamey, mike.auty |
Version: | git | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Lars Knoll
2006-10-10 03:59:43 UTC
There are many locking bugs in the Xlib... :-) The XFixes change was obviously correct, so I pushed it. I haven't found any documentation on whether event filter callbacks are supposed to have the Display lock or not, so I can't tell if the libX11 change is correct. At the moment I'm not sure how to proceed with that. (In reply to comment #1) > There are many locking bugs in the Xlib... :-) > > The XFixes change was obviously correct, so I pushed it. > > I haven't found any documentation on whether event filter callbacks are supposed > to have the Display lock or not, so I can't tell if the libX11 change is > correct. At the moment I'm not sure how to proceed with that. The callback goes back into application space. From there you could in theory call almost any Xlib function. This is IMO a strong argument for unlocking before the callback. Second half committed. Thanks! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.