• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Core Data: rare exception
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data: rare exception


  • Subject: Re: Core Data: rare exception
  • From: Ricardo Strausz <email@hidden>
  • Date: Mon, 8 Oct 2007 17:04:01 -0500

Thx Jim, but not too helpful...

I am not writing a single line of code, therefore if it is a bug, it is a Core Data's bug... and I cannot fix it;
however, my impression is that it may have to be with the relations in my model...
do I have to make some of them mandatory?
may be some deleting rule?
some not obvious attribute I have to set?


Thanks again,
Dino

On Oct 8, 2007, at 4:37 PM, Jim Correia wrote:

On Oct 8, 2007, at 5:26 PM, Ricardo Strausz wrote:

I am playing with a Core Data Document based app and found that, while running and trying to add: an object, the following error message appears in the console

2007-10-08 16:13:57.799 CDD_Curare[1945] *** -[NSCFDictionary _isMaintainingInverse]: selector not recognized [self = 0x3367b0]
2007-10-08 16:13:57.800 CDD_Curare[1945] *** NSRunLoop ignoring exception '*** -[NSCFDictionary _isMaintainingInverse]: selector not recognized [self = 0x3367b0]' that raised during posting of delayed perform with target 3b3150 and selector 'invokeWithTarget:'


Does anybody recognises this?

This is really a FAQ.

Whenever you see SomeClass: selector not recognized and the selector in question is a) not something you sent directly and b) recognizable as a selector for some other sort of object, a very common cause of this is a memory management bug. What typically is happening is that there used to be a instance ClassA at that address, but it has gone away, and now there is an instance of ClassB. Someone has a stale pointer to the object and is messaging it.

NSZombie is a good first step for tracking down the problem.

Jim


_______________________________________________

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


  • Follow-Ups:
    • Re: Core Data: rare exception
      • From: "I. Savant" <email@hidden>
    • Re: Core Data: rare exception
      • From: Jim Correia <email@hidden>
References: 
 >Core Data: rare exception (From: Ricardo Strausz <email@hidden>)
 >Re: Core Data: rare exception (From: Jim Correia <email@hidden>)

  • Prev by Date: Re: DEUG vs RELEASE
  • Next by Date: Re: DEUG vs RELEASE
  • Previous by thread: Re: Core Data: rare exception
  • Next by thread: Re: Core Data: rare exception
  • Index(es):
    • Date
    • Thread