Summary: | xcb not re-enterant ... blocking desktop ... | ||
---|---|---|---|
Product: | XCB | Reporter: | Michael Meeks <michael.meeks> |
Component: | Library | Assignee: | xcb mailing list dummy <xcb> |
Status: | RESOLVED NOTOURBUG | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | critical | ||
Priority: | medium | CC: | eich, mat, sndirsch |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Michael Meeks
2010-02-24 05:43:31 UTC
I would have thought that calling any Xlib function from a signal handler was unsafe... (In reply to comment #1) > I would have thought that calling any Xlib function from a signal handler was > unsafe... Absolutely - Xlib has never been async-signal safe. Very few library functions are (see the list in the POSIX/UNIX specs). 16:03 < jcristau> hrm. is XSync() really supposed to be ok to call from a signal handler? 16:03 < jcristau> (bug 26728) 16:05 < ajax> jcristau: almost certainly not. 16:05 < jcristau> that's what i thought 16:05 < ajax> if you're in the middle of generating some other protocol, you'll fuck up the protocol stream 16:05 < ajax> more generally, deadlocks ahoy. closing as not our bug. don't do that. Thanks for the prompt replies! :-) |
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.