[Bug 1944] RtlpWaitForCriticalSection wait timed out in thread
Wine Bugs
wine-bugs at winehq.org
Mon Jan 19 16:46:18 CST 2004
http://bugs.winehq.org/show_bug.cgi?id=1944
------- Additional Comments From marcus at jet.franken.de 2004-19-01 16:46 -------
from reporter:
Maybe it relies too much on glibc style threadsafe model.
In FreeBSD it is definitely not using glibc. The libraries
loaded by default are...
(mjolnir) 10:42 ~> ldd `which wine`
/usr/local/bin/wine:
libwine.so.1 => /usr/local/lib/libwine.so.1 (0x20130000)
libc.so.4 => /usr/lib/libc.so.4 (0x20148000)
libm.so.2 => /usr/lib/libm.so.2 (0x201e1000)
Actually I suppose the libc.so should be libc_r.so for FreeBSD
environments.
I am not quite convinced that libc.so really guarantees that
everything is really thread safe by any standards. Full POSIX
threadsafe model is supported by libc_r.so, which becomes
automatically linked in when the -pthread option is give to
cc/gcc. Obviously the objects should also be compiled using
the -D_THREAD_SAFE option.
If this is the explanation to the odd behaviour, this looks
like the automatic configure makes some false assumptions for
FreeBSD.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the wine-bugs
mailing list