On Sat, 13 Mar 2010 16:46:28 -0500, Steven Degutis
said:
>This is almost always caused by releasing an object earlier than you
>expected to, and then trying to release it again later (similar to "double
>free"). Look around in your class's code
Wouldn't this be clearly called out by use of NSZomb
Spot on, Steven. My memory management was faulty. My object had been
instantiating another object via alloc that it kept a reference to in an iVar,
and my (outer) object released that instantiated (inner) object in its -dealloc
method. I refactored the code, and changed the way I acquire the (in
This is almost always caused by releasing an object earlier than you
expected to, and then trying to release it again later (similar to "double
free"). Look around in your class's code for a place where you autorelease
an ivar, but don't add it to a collection, or where you release an ivar but
don'
I have some code that is throwing EXC_BAD_ACCESS. It does so when an object is
deallocating, in its -dealloc method on a call to [super dealloc]. The object's
class's superclass is NSObject. Here's the (relevant part of the) stack trace:
#0 0x7fff872e016d in _class_hasCxxStructorsNoSuper
#1
