Re: The mutex is twice locked in different threads
Re: The mutex is twice locked in different threads
- Subject: Re: The mutex is twice locked in different threads
- From: Wade Tregaskis <email@hidden>
- Date: Thu, 16 Jul 2009 10:26:27 -0700
PreLock thread(1822400) id(sync_report_9AC72CBD) owner(0)
lock_count(0)
Lock thread(1822400) id(sync_report_9AC72CBD) owner(1822400)
lock_count(1) error(0)
PreLock thread(181be00) id(sync_report_9AC72CBD) owner(1822400)
lock_count(1)
Lock thread(181be00) id(sync_report_9AC72CBD) owner(181be00)
lock_count(1) error(0)
PreUnlock thread(1822400) id(sync_report_9AC72CBD) owner(181be00)
lock_count(1)
Unlock thread(1822400) id(sync_report_9AC72CBD) owner(181be00)
lock_count(1) error(1)
Is this all you have? This doesn't prove double-locking; it's almost
certainly just races and out of order log messages. Your PreLock
seeing the old owner is just a race, and your PreLock+Lock appearing
before the unlock is just your printfs being interleaved.
You'd be better off using something like Shark's System Trace to look
at this; you'll be able to see much more reliably what your locking
patterns are (assuming there's actually any lock contention).
What is the problem you're seeing that leads you to believe the lock
is failing so?
Wade
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden