[Xcb] [Bug 23192] racy access to dpy->synchandler in libX11 >=

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 21 18:30:06 PDT 2010


--- Comment #9 from Steve R <fdsteve at ihug.co.nz> 2010-04-21 18:30:05 PDT ---
After my comment #1, I too found the problem with the recursive LockDisplay. I
managed to fix that issue, but overall my fix only ever worked 95%, so I look
forward to testing this out.

One other thing I wondered at the time is to do with the assert( (dpy->flags &
XlibDisplayPrivSync) != 0 )
Are bitwise flag modifications gaurenteed to be atomic??? 
Not all the other flags are modified within LockDisplays.
ie Could a read/modify/write to one of the other flags make the
XlibDisplayPrivSync flag un-thread-safe?

Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the Xcb mailing list