Re: Suggestions for debugging “EXC_BAD_ACCESS”
Re: Suggestions for debugging “EXC_BAD_ACCESS”
- Subject: Re: Suggestions for debugging “EXC_BAD_ACCESS”
- From: Greg Parker <email@hidden>
- Date: Fri, 25 Sep 2009 12:36:03 -0700
On Sep 25, 2009, at 12: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? I've tried running with the performance
tools, which tells me where objects are allocated, but I haven't
found anything that will help identify THE object that's causing the
problem. I've tried Shark, but it just seems to hang with
"Sampling...". Any and all suggestions welcome.
Try NSZombies first. Guard Malloc catches some errors that NSZombie
does not. You can also dig around in the CPU register data:
http://sealiesoftware.com/blog/archive/2008/09/22/objc_explain_So_you_crashed_in_objc_msgSend.html
--
Greg Parker email@hidden Runtime Wrangler
_______________________________________________
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