Re: is ObjectAlloc broken?
Re: is ObjectAlloc broken?
- Subject: Re: is ObjectAlloc broken?
- From: Ken Victor <email@hidden>
- Date: Thu, 20 Oct 2005 11:32:29 -0700
thanx for the reply.
yes, i do call {super dealloc]. i didn't think
those warnings would cause this problem, but i
included them for completeness, just in case...
i've done a little more checking. this same
problem, ie objectAlloc apparently showing
incorrect counts, shows up for other objects in
my app that also call dealloc. i'm pretty sure
i've run objectAlloc in the past and noticed
correct behavior for some of the objects that are
now showing apparently wrong counts.
unfortunately, i don't remember how long ago that
was.
it appears to me that objectAlloc is broken with
xcode 2.1, X 10.4.2. is anyone else experiencing
either success or similar problems?
thanx,
ken
At 8:21 AM +0200 10/20/05, Elias Mårtenson wrote:
20 okt 2005 kl. 01.43 skrev Ken Victor:
i have an object and i've put calls to nslog at
it init and dealloc methods and in fact it is
being allocated/inited once and being dealloced
once. however, when i run under ObjectAlloc
(xcode 2.1; OS X 10.4.2) it shows a current and
peak and total count of 1, even after my
alloc/init/dealloc.
Did you forget to put a [super dealloc] at the end of your dealloc method?
The warnings you got has nothing to do with your problem.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden