http://bugs.winehq.org/show_bug.cgi?id=34367
--- Comment #12 from Carlo Marchiori carlo.marchiori@gmail.com 2013-09-03 06:03:49 CDT --- Created attachment 45833 --> http://bugs.winehq.org/attachment.cgi?id=45833 After all I think it's a wine bug
Hello,
take a look at the attached stacktrace... ups... backtrace (oh my, yes, I'm a Java developer). I think it shows that after all it could be a problem with wine, or somewhere in between.
x11drv_init_thread_data sets up thread related information and ends up calling X11DRV_SetupXIM in libX11. But IM (Input Method) is coded statically, it saves IM state in static variables (global library scope) and, as far as I can see, it does it unprotected by locks.
winex11.drv/xim.c says
329 /*********************************************************************** 330 * X11DRV Ime creation 331 * 332 * Should always be called with the x11 lock held 333 */ 334 static BOOL open_xim( Display *display )
but is it?