Re: Suggestions for debugging “EXC_BAD_ACCESS” [SOLVED]
Re: Suggestions for debugging “EXC_BAD_ACCESS” [SOLVED]
- Subject: Re: Suggestions for debugging “EXC_BAD_ACCESS” [SOLVED]
- From: Bob Barnes <email@hidden>
- Date: Fri, 25 Sep 2009 16:46:45 -0700
Kyle/Nick/Greg,
Thank you guys. Took a little digging but the combination of
NSZombie & instruments object allocation did the job. After years
working with Java I find myself tripping over memory management issues
much too often. I had allocated a UIButton using buttonWithType: and
then later released it without ever having retained it. I'm
concluding (perhaps incorrectly) that using buttonWithType: doesn't
grant 'object ownership' in the same way that alloc does.
Bob
On Sep 25, 2009, at 12:36 PM, Greg Parker wrote:
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