Date: Sun, 25 Jun 2006 22:17:35 +0200 (CEST) From: Gerald Pfeifer <gerald@pfeifer.com> To: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> Cc: freebsd-ports@freebsd.org Subject: Re: latest wine-kthread broken? Message-ID: <Pine.LNX.4.61.0606252215240.6301@acrux.dbai.tuwien.ac.at> In-Reply-To: <449CEB97.5020903@gmx.de> References: <449CEB97.5020903@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 24 Jun 2006, [LoN]Kamikaze wrote: > The games Starcraft and Diablo 2 which were running fine using > wine-kthread up to this mornings portupgrade, now simply halt (infinite > loop maybe), even CTRL-C doesn't kill them. I have to stop them using > 'killall -9 wine-kthread'. This is the only output: > > Fatal error 'Uninitialized mutex in pthread_mutex_trylock_basic' at line > 496 in file /mnt/vault/src/lib/libpthread/thread/thr_mutex.c (errno = 2) > > I always thought the purpose of kthread is not to use pthread. Thus I > presume that the latest version of wine (wine-0.9.16,1) is broken. This may well be. However, GNU/Linux systems using the pthread variant, there is little hope anyone is ever going to fix the kthread variant. I have included the kthread variant as an added benefit, but all development and bug fixing really should go into the pthread variant. You did not mention whether this works for your applications, but I assume it does not? Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.61.0606252215240.6301>