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: Kyle Sluder <email@hidden>
- Date: Fri, 19 Jun 2009 09:42:34 -0700
On Fri, Jun 19, 2009 at 9:18 AM, Jerry Krinock<email@hidden> wrote:
> That should do the job, right?
You're better off setting it in the executable's inspector. Do a Get
Info on your executable and you'll see an Environment Variables
section.
> As you can see, the last thing I do there is get the -managedObjectContext
> of my NSPersistenDocument of subclass Bookshelf. But I haven't touched that
> code in months. It must be a smasher.
Not necessarily. Could be a threading issue. Are you multithreaded?
> Usually, nothing is logged the console except the gdb splash/license. One
> time, though, I got this "all hell broke loose":
If you break in objc_msgSend, you can get self using `po *(id **)($ebp+8)`.
> As expected, correcting the signature of my -isEqual: to take id as an
> argument instead of Browfile* did not help.
This really isn't a change. Codegen isn't affected if you change the
argument from id to a specific object pointer type. Both just thunk
down to `struct objc_class *`.
> Again, I "touched" all the files, rebuilt everything, and didn't get any
> warnings of multiple method implementations.
Try doing a "Clean All."
--Kyle Sluder
_______________________________________________
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