[Fwd: Re: Xorg: Xim deadlock in threaded apps]
Alan Coopersmith <Alan.Coopersmith-UdXhSnd/[email protected]>
| Newsgroups | gmane.comp.freedesktop.release-wranglers |
|---|---|
| Message-ID | <[email protected]> |
This is the response I got from our Xi18n experts on the Xim deadlock issue. -alan- -------- Original Message -------- Subject: Re: Xorg: Xim deadlock in threaded apps Date: Fri, 27 Aug 2004 13:35:36 -0700 From: Hidetoshi Tajima <Hidetoshi.Tajima-UdXhSnd/[email protected]> Hi Alan, As Egbert commented, we cannot predict which Xlib functions are called from XFilterEvent(). It's up to XIM implementation, under XI18N pluggable interface. In our implementation, we don't LockDisplay()/UnlockDisplay() in XFilterEvent(), since XFilterEvent() itself does not issue any requests to Xserver, hence no needs to lock the display connection. The bug is #4041914. As you see the bugid, we've done so almost 8 or 9 years on Solaris. Can we suggest this as an alternative solution? Regards, Toshi Alan Coopersmith wrote: > Egbert has asked that someone with more knowledge of the Xlib i18n code > review this patch for X.org to determine if it should go into the X11R6.8 > release (currently planned for next week): > http://freedesktop.org/bugzilla/show_bug.cgi?id=1182 > > Please add comments to the bug report in bugzilla if you have a chance to > look at it - any sort of review comment, positive or negative, would be > helpful. (Also, if this is something we need to bring into our Xlib, > please let us know and/or file a report in bugtraq.) > > Thanks, > > -alan- >