Re: death in dealloc
Re: death in dealloc
- Subject: Re: death in dealloc
- From: Steven Degutis <email@hidden>
- Date: Sat, 13 Mar 2010 16:46:28 -0500
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't set it to nil afterwards.
-Steven
On Sat, Mar 13, 2010 at 12:53 PM, Stuart Malin <email@hidden> wrote:
> 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 0x7fff872e0741 in object_cxxDestructFromClass
> #2 0x7fff872e60f8 in objc_destructInstance
> #3 0x7fff872e06f5 in _internal_object_dispose
> #4 0x7fff83e0279a in -[NSObject(NSObject) dealloc]
> #5 0x10007b18e in -[ZPOauthParams dealloc] at ZPOauthParams.m:57
>
> I know I must have blown something, but I have no idea what I could have
> done to cause this sort of problem. If anyone has seen something like this
> before, please let me in what direction I should look for the problem. TIA.
>
> _______________________________________________
>
> 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
>
--
Steven Degutis
http://www.thoughtfultree.com/
http://www.degutis.org/
_______________________________________________
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