Re: file scan results in EX_BAD_ACCESS
Re: file scan results in EX_BAD_ACCESS
- Subject: Re: file scan results in EX_BAD_ACCESS
- From: Daniel Child <email@hidden>
- Date: Sat, 01 Sep 2007 11:08:14 -0400
No, it was [super dealloc]. Here is the code. Maybe I shouldn't check
for (self) ?Sorry if this is an obvious mistake. I'm still trying to
get the basic memory management idioms down.
- (void) dealloc
{
[self setFieldDelim: nil];
[self setRecordDelim: nil];
if (self) [self release];
[super dealloc];
}
On Aug 31, 2007, at 10:49 PM, Fritz Anderson wrote:
So the code you want to show us is -[DataParser dealloc]. Evidently
it's calling itself.
Did you close it out with [self dealloc] instead of [super dealloc]?
— F
On Aug 31, 2007, at 9:28 PM, Daniel Child wrote:
I was stepping through until it hits the while loop. A breakpoint
after that shows that the error appears to occur at [pool
release]. After canceling the thread stack message, there is a #0
thread that reads: NSDecrementExtraRefCountWasZero., followed by 1
[NSObject release] and a gazillion [DataParser dealloc]s.
_______________________________________________
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