Re: How to debug crash in NSOperation?
Re: How to debug crash in NSOperation?
- Subject: Re: How to debug crash in NSOperation?
- From: "Gerriet M. Denkmann" <email@hidden>
- Date: Tue, 28 Mar 2017 10:50:43 +0700
Sent from my iPhone
> On 28 Mar 2017, at 10:32, Jens Alfke <email@hidden> wrote:
>
>
>> On Mar 27, 2017, at 8:25 PM, Gerriet M. Denkmann <email@hidden> wrote:
>>
>>
>>
>> Sent from my iPhone
>>
>>> On 27 Mar 2017, at 23:37, Jens Alfke <email@hidden> wrote:
>>>
>>>
>>>> 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.
>>
>> This same error occurred twice within 250 days. Running the code for about a year in Xcode is really not feasible.
>
> But when it did occur, it was hard to figure out what was going on, right?
No, not really. It was just my stupidity of reading the crash log right.
It clearly showed that it crashed when I asked a Filewrapper (which contains about 6 sub wrappers which represent files) for serialised data.
And one of these subwrappers (which were being put into an NSDictionary) turned out to be nil.
Kind regards,
Gerriet
_______________________________________________
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