• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Understanding Application crash
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Understanding Application crash


  • Subject: Re: Understanding Application crash
  • From: Jens Alfke <email@hidden>
  • Date: Mon, 24 Mar 2014 22:55:47 -0700

On Mar 24, 2014, at 10:48 PM, Appa Rao Mulpuri <email@hidden> 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 (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


References: 
 >Re: Understanding Application crash (From: Appa Rao Mulpuri <email@hidden>)

  • Prev by Date: Re: Understanding Application crash
  • Next by Date: Re: Creating NSViewController with -init.
  • Previous by thread: Re: Understanding Application crash
  • Next by thread: Re: Understanding Application crash
  • Index(es):
    • Date
    • Thread