site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Wade _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... 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? This email sent to site_archiver@lists.apple.com