Handling of client-side multi-threading in X
Locking in X libraries
[Describe here what kind of locking is needed by X libs and how it's implemented]
- --disable-xthreads disables threads support in libX11 (default: enabled).
Defined and used by X:
- XTHREADS defined whenever libX11 is built with threads support.
XUSE_MTSAFE_API defined if libc has getpwuid_r() and getpwnam_r()
Used by OS headers and set by X:
There are several X headers related to threads
[Describe here the role of <X11/Xos_r.h> and when it needs to be included.]
[Describe here the role of <X11/Xthreads.h> and when it needs to be included.]
Xlib and the associated libraries can support various threading libraries from the operating system they run on.
- POSIX pthreads
- Microsoft Windows threads
- DEC Threads
Support for both threaded and non threaded applications
Since not all systems support threads by default in their basic C libraries, Xlib has some support for emulating threads support when it's not present in libc, so that the same library can be used in applications built with or without thread support.
This support is provided throught a set of weak symbols function pointers that define stub implementatons of the threading functions that may be called by thread-aware code. When a real theading implementation is present, the weak definitions are ignored, and the code will call the real functions from the system's threading library. If on threading implemnentation the stubs functions pointed at by the weak symbols will be called. Those stubs are no-op that only make sense in a thread-less environment of course.
Those stubs are implemented for various systems in UIThrStubs.c
[Describe here how using XCB alone or XCB -enabled libX11 changes things]