Re: Just implementing -isEqual:, never invoked, causes crash
Re: Just implementing -isEqual:, never invoked, causes crash
- Subject: Re: Just implementing -isEqual:, never invoked, causes crash
- From: Michael Ash <email@hidden>
- Date: Fri, 19 Jun 2009 11:55:05 -0400
On Fri, Jun 19, 2009 at 11:40 AM, Jerry Krinock<email@hidden> wrote:
> I implemented an -isEqual: method in one of my classes today. This causes
> the app to crash while loading a document, after some milliseconds. Crashes
> occur in different unrelated places.
>
> I then simplified the implementation to just log and call super --
>
> - (BOOL)isEqual:(Browfile*)otherBrowfile {
> NSLog(@"isEqual???") ;
> return [super isEqual:otherBrowfile] ;
> }
>
> Or, return a constant --
>
> - (BOOL)isEqual:(Browfile*)otherBrowfile {
> NSLog(@"isEqual???") ;
> return NO ;
> }
>
> Crashes either way, and the log statement in there never logs.
>
> Simply removing this implementation by renaming it to XXisEqual: results in
> no more crashes. The crash looks like a memory-smasher, but under the
> circumstances maybe something is being linked incorrectly. I "touched" all
> of the files and re-built, and did not get any "multiple implementations --
> using this one" warnings.
>
> I've implemented -isEqual: in several other of my classes with no problems.
> What in the world could do this?
>
> Please make my day by giving me ^something^ to chew on here.
You need to give us something to chew on first. Showing your code is
good, but for some unfathomable reason you left out all the crash logs
that you referred to. You also haven't mentioned anything you did to
try to track this problem down beyond renaming the method.
Mike
_______________________________________________
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