Hello, you might place some breakpoints, you did only post the
consequences, debugging is matter of understanding.
On Sun, Jun 13, 2010 at 8:49 AM, Gideon King wrote:
> I have a situation where I create a temporary managed object context and do a
> bunch of things with various managed objects
Thanks Jerry
>
> Whoops/sorry. I forgot that -[NSManagedObject valueForKey:] is an Apple
> method so all you get is stupid registers and no symbols. (Text is not
> colorized in email.)
>
> So there are two ways to do this. One way would be, assuming that all of
> your managed objects desce
On 2010 Jun 13, at 17:34, Gideon King wrote:
> From the top down approach, the places I could envisage this problem
> originating are:
> 1. NSNotificationQueue - queued notifications that get fired after I have
> released the MOC, and the objects have been faulted and invalidated but not
> rem
Thanks Jerry & mm
@mm The problem is I don't know what to put breakpoints on
@jerry My understanding is that with the core data, they have their own memory
management scheme which will reuse the space of something that has been
invalidated, and that invalidated is not equal to deallocated. If I
On 2010 Jun 13, at 08:49, Gideon King wrote:
> I get an exception ... The NSManagedObject with ID:(whatever) has been
> invalidated.
Those things always ruin my day. I don't think I've ever fixed one by
debugging from the bottom up as you would like to do. The solution has always
come from t
