• 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: problem unit testing core data
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problem unit testing core data


  • Subject: Re: problem unit testing core data
  • From: Jesse Grosjean <email@hidden>
  • Date: Wed, 26 Oct 2005 15:57:30 -0400

You might want to implement and/or put a breakpoint in the
didTurnIntoFault method on your managed object subclass:  this method
will be called on each object invalidated in the context (as a result
of the deallocation), and you should be able to see all of the
"ContextIndex" objects which are going to be tossed.  (You could try
logging all of the object IDs and something more meaningful, to then
correlate against the ID information in the exception later to get a
better idea of which one is being accessed, and then why ...)

Matthew,

Thanks, that found the problem! I had already overridden didTurnIntoFault in one of my classes and some of that code was causing the problem. But for some reason it didn't effect things when running the application normally, and didTurnIntoFault wasn't showing up in any of the stack traces when running unit tests. Anyway thanks again, it's fixed now.

Jesse
_______________________________________________
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


  • Prev by Date: Custom framework and Interface Builder.
  • Next by Date: Re: anyone looking to hire cocoa developers?
  • Previous by thread: Re: problem unit testing core data
  • Next by thread: performSelectorOnMainThread
  • Index(es):
    • Date
    • Thread