Re: How to Control App Crashing
Re: How to Control App Crashing
- Subject: Re: How to Control App Crashing
- From: Jens Alfke <email@hidden>
- Date: Wed, 9 Jul 2008 08:23:00 -0700
On 9 Jul '08, at 3:12 AM, SridharRao M wrote: Hi,
I tried by using breakpoint on -[NSException raise] and objc_exception_throw. still giving same exception.
*** -[NSCFType count]: unrecognized selector sent to instance 0x47bae0 2008-07-09 15:14:38.737 iSoundTest[2330:20b] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSCFType count]: unrecognized selector sent to instance 0x47bae0' Exceptions like this one — a common message like -count being sent to some random object that doesn't understand it, from inside framework code — are most often caused by an object getting dealloced too early. The next time that object pointer gets called, it is likely to point to a different, newer object.
To debug this, look up Technote 2124 in the documentation viewer, scroll to the "Foundation" section, and read the docs on using NSZombieEnabled.
—Jens
PS: And please get a clue about not using the word "*Ph*n*" in public lists! You've been warned several times already. |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden