Re: NSRecursiveLock problems
Re: NSRecursiveLock problems
- Subject: Re: NSRecursiveLock problems
- From: PCWiz <email@hidden>
- Date: Tue, 22 Dec 2009 11:53:20 -0700
Scrap that, I managed to find where the problem is happening. Debugger:
http://img709.imageshack.us/img709/9758/screenshot20091222at115.png
I didn't know that NSInvocationOperation used NSRecursiveLock. But this still doesn't really help me understand *why* I'm getting these errors. The use of NSInvocationOperation seems quite simple, so I'm not seeing where this is going wrong. You can see the code where I invoke the operation in the screenshot.
Independent Cocoa Developer, Macatomy Software
http://macatomy.com
On 2009-12-22, at 11:49 AM, PCWiz wrote:
> Lately I've been getting errors like these with my app:
>
> 2009-12-21 13:07:48.420 TwitMenu[2512:a0f] *** -[NSRecursiveLock unlock]: lock (<NSRecursiveLock: 0x20069d980> '(null)') unlocked when not locked
> 2009-12-21 13:07:48.420 TwitMenu[2512:a0f] *** Break on _NSLockError() to debug.
> 2009-12-21 13:07:48.437 TwitMenu[2512:4103] *** -[NSRecursiveLock finalize]: lock (<NSRecursiveLock: 0x20069dca0> '(null)') finalized while still in use
> 2009-12-21 13:07:48.437 TwitMenu[2512:4103] *** Break on _NSLockError() to debug.
>
> As Greg Parker suggested in an earlier question, instead of putting a breakpoint on NSLockError (which doesn't work) I put a breakpoint on NSLog. And this is what the debugger looks like:
>
> http://img30.imageshack.us/img30/5894/screenshot20091222at114.png
>
> I dont see how any code in there has a connection to NSRecursiveLock.
>
> Independent Cocoa Developer, Macatomy Software
> http://macatomy.com
>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden