Add note in man-page that XListFontsWithInfo is not thread-safe.

_XReply drops the Display lock, so the value of dpy->request may change
before _XReply is called again.

I discovered this by inspection a year or two ago. I'm pretty confident
in the claim, and nobody has come up with an argument for why it's safe
despite appearances.
This commit is contained in:
Jamey Sharp 2006-11-21 17:52:34 -08:00
parent 67abe02426
commit a1168e11ec

View file

@ -253,6 +253,12 @@ is passed, the structure is freed,
but the font is not closed; use
.ZN XUnloadFont
to close the font.
.LP
Note that
.ZN XListFontsWithInfo
is not thread-safe. If other threads make X requests on the same
.ZN Display ,
then this function's behavior is undefined.
.SH "SEE ALSO"
XLoadFont(3X11),
XSetFontPath(3X11)