Date: Sat, 22 Jul 2006 19:15:35 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Michael Nottebrock <lofi@freebsd.org> Cc: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org, kmacy@fsmware.com Subject: Re: WINE vs. FreeBSD Message-ID: <Pine.GSO.4.64.0607221912140.4394@sea.ntplx.net> In-Reply-To: <200607222341.05180.lofi@freebsd.org> References: <200607221914.15826.lofi@freebsd.org> <b1fa29170607221220j7638a5e7l324bf4cc48dffdf7@mail.gmail.com> <200607222341.05180.lofi@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 22 Jul 2006, Michael Nottebrock wrote: > On Saturday, 22. July 2006 21:20, Kip Macy wrote: >> Thanks for your input. >> >> The relative merits of the different threading libraries is currently >> under discussion. Could you also try it with libthr (it may not work >> at all), I'd like to hear what happens. Thanks. > > WINE crashes in roughly the same spot. This is however with a libthr on > FreeBSD 5.5-RELEASE-p2, which is nothing short of disastrous (with a global > lib mapping from libpthread to libthr, about 1/3 of all the programs in my > default KDE session start at all - the rest hangs in state sbwait). I think it is because WINE stomps on or TLS. Nothing we can do about that except patch wine so it doesn't. Look at the console messages for: Warning: pid XXX used static ldt allocation -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0607221912140.4394>