How to find out locking problem
damjan.jov at gmail.com
Mon Jan 3 09:30:46 CST 2011
On Sun, Jan 2, 2011 at 7:36 PM, Henri Verbeet <hverbeet at gmail.com> wrote:
> On 2 January 2011 17:43, <wylda at volny.cz> wrote:
>> The truth is, that wine outputs the first line ("...wait timed out
>> in thread 001c, blocked by 0041...") only once and after that only
>> the 2nd line repeats every 60sec ("...wait timed out in thread 0045,
>> blocked by 0044..."). Don't know if that's normal in these cases or
>> both lines should repeated.
> Thread 0041 is probably just a bit slow at some point then, but it
> does sound like it eventually releases the lock. It would be
> interesting to figure out what's taking so long, but it's probably not
> the main problem.
> For a proper deadlock you'd have at least two threads waiting for each
No, a sufficient condition for a deadlock is that a thread waits for
something that will never happen. It could be waiting for a lock to be
released, but that thread itself already holds the lock. Or another
thread took the lock but died before releasing it.
More information about the wine-devel