Re: Works in 4.1 but not 4.2 ...
Re: Works in 4.1 but not 4.2 ...
- Subject: Re: Works in 4.1 but not 4.2 ...
- From: Matt Neuburg <email@hidden>
- Date: Thu, 2 Dec 2010 10:37:32 -0800
On Thu, 2 Dec 2010 06:38:31 -0600, James Cicenia <email@hidden> said:
>Yes .. but why did it like it prior to my upgrade?
>
Don't confuse the compiler with the runtime. You can put anything past the compiler. What matters is what's true at runtime. The crash log suggests that you are not sending the message setController: to the instance you think you're sending it to. That's probably because you've got a memory management bug. You likely over-released something earlier (you can turn on zombies to track that down; also don't forget to use build & analyze). It's just chance whether that bug shows up and bites you at any particular moment. So, if that's the cause, you had this bug in 4.1 too but you were just lucky and it wasn't yet being exposed. m.
>>> 2010-12-02 06:11:40.705 CoinStar[31673:207] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[UIView setController:]: unrecognized selector sent to instance 0x9814950'
m.
--
matt neuburg, phd = email@hidden, <http://www.apeth.net/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.apeth.net/matt/default.html#applescriptthings_______________________________________________
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