• 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: Suggestions for debugging “EXC_BAD_ACCESS”
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Suggestions for debugging “EXC_BAD_ACCESS”


  • Subject: Re: Suggestions for debugging “EXC_BAD_ACCESS”
  • From: Nick Zitzmann <email@hidden>
  • Date: Fri, 25 Sep 2009 13:27:41 -0600


On Sep 25, 2009, at 1:14 PM, Bob Barnes wrote:

If I'm reading this correctly, not a given by any means, Core Foundation is trying to get the retain count for an object, possibly a CALayer, where the reference pointer is no longer valid, but how do I determine what object?

Use Instruments, use the object alloc instrument with retain/release counting and NSZombie detection turned on, and run your app. When it crashes, you should be told what caused the crash, and you should get a complete log of the retains/releases on the object.


Nick Zitzmann
<http://www.chronosnet.com/>

_______________________________________________

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: 
 >Suggestions for debugging “EXC_BAD_ACCESS” (From: Bob Barnes <email@hidden>)

  • Prev by Date: Re: Parsing error in NSEvent?
  • Next by Date: Re: Suggestions for debugging “EXC_BAD_ACCESS”
  • Previous by thread: Re: Suggestions for debugging “EXC_BAD_ACCESS”
  • Next by thread: Re: Suggestions for debugging “EXC_BAD_ACCESS”
  • Index(es):
    • Date
    • Thread