Re: How to debug crash in NSOperation?
Re: How to debug crash in NSOperation?
- Subject: Re: How to debug crash in NSOperation?
- From: Jens Alfke <email@hidden>
- Date: Mon, 27 Mar 2017 09:37:21 -0700
> On Mar 26, 2017, at 10:04 PM, Gerriet M. Denkmann <email@hidden> wrote:
>
> Yes, you are right. And I have to apologise for not spotting this:
>
> *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** setObjectForKey: object cannot be nil (key: SortedKeys.plist)'
I recommend always having an exception breakpoint set, to catch things like this.
> I suspect that this might be a rare timing issue, i.e. SortedKeys.plist has not been fully written when serializedRepresentation is called.
Is the snippet you posted all code running in the same thread/queue? If so, there couldn’t be a race condition between writing the plist and reading it. If not, you need some synchronization between the two operations (the specifics would depend on the details of your program.)
—Jens
_______________________________________________
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