Re: Problem tracking crash in iOS
Re: Problem tracking crash in iOS
- Subject: Re: Problem tracking crash in iOS
- From: Laurent Daudelin <email@hidden>
- Date: Wed, 16 Nov 2011 15:10:46 -0800
Thanks, Doug, I had started looking at this but will definitely put all my attention on why the original observer wouldn't be there to receive the notification, although, so far, I can't see how it would be deallocated.
-Laurent.
--
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin http://www.nemesys-soft.com/
Logiciels Nemesys Software email@hidden
On Nov 16, 2011, at 14:57, Doug Hill wrote:
> When you see notifications being sent to random objects, it usually means the original registered observer object was deallocated without removing the observer for the notification. The notification is then sent to a random object that now resides in the reused space formerly occupied by the original observer. I would check if you're removing your observers first before getting too crazy with debugging.
>
> Doug Hill
> Schematic Labs, Inc.
> http://soundtracking.com/
>
> On Nov 16, 2011, at 2:23 PM, Laurent Daudelin wrote:
>
>> I'm working on an app with a bug that is reproducible each time. Some object is trashed and the NSNotificationCenter tries to send a notification to an object that doesn't respond to that selector. I turned on NSZombieEnabled and a bunch of other settings for my debug session but when I turn on NSZombieEnabled, the crash doesn't occur and the app keeps running.
>>
>> How can I find out which object is wrongly deallocated? And no, I didn't write the app...
>>
>> Thanks in advance!
>>
>> -Laurent.
>> --
>> Laurent Daudelin
>> AIM/iChat/Skype:LaurentDaudelin http://www.nemesys-soft.com/
>> Logiciels Nemesys Software email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden