On Mar 24, 2014, at 10:48 PM, Appa Rao Mulpuri <appar...@ivycomptech.com> wrote:
> Agreed, Since this exception is getting rarely. Do we have any provision > to extend the stack trace to print in which method the object is getting > deallocated in our class? Look up NSZombieEnabled, although that’s not really something you can use in a production build of the app since it causes massive memory leaks. So you may have to just look at your code and try to reason about it — What control is it likely to be? What object was the target of that control? Who retains/releases objects of that class? And so on. —Jens _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
