Re: How to find out locking problem

[James McKenzie]

On 1/1/11 7:10 PM, Dan Kegel wrote:
> Sometimes it helps to run winedbg from another window
> and get the stacks of all running processes with the command
>    bt all
> With luck, you can then see which two code paths are
> competing for the lock.

Dan:

I've also been getting random 'locks' and this is only running 'make 
test' and that resulted in an update to the Wine Configuration.  This 
looks like a regression of the problem that was fixed a long time ago, 
where interprocess locking happened constantly.  Maybe Wylda can find 
it, if the problem is constant on his system.

James McKenzie