Re: Crash as NSPersistentDocument creates its persistence stack

On 2009 Jan, 07, at 10:40, mmalc Crawford wrote: The error seems to correctly describe the problem... Department is in a separate model (MyDocument) that you must include in order for the entity to be found in: Yes, you're correct mmalc. I didn't watch that carefully enough, and this wa

Re: Crash as NSPersistentDocument creates its persistence stack

On Jan 7, 2009, at 9:56 AM, Jerry Krinock wrote: Problem ID number 6478155. Using the project as provided, you get the same error -- 2009-01-07 09:40:51.689 DepartmentAndEmployees[27205:10b] +entityForName: could not locate an entity named 'Department' in this model. whichever of Model

Re: Crash as NSPersistentDocument creates its persistence stack

On 2008 Dec, 25, at 22:55, Jerry Krinock wrote: So, tomorrow I'm going to copy all of my old files to the new project and I expect that it will work again. Oh well, the project was in need of a renaming and a housecleaning anyhow. Just in case anyone else has this problem, be advised that

Re: Crash as NSPersistentDocument creates its persistence stack

On 2008 Dec, 24, at 0:03, mmalc Crawford wrote: Thank you, mmalc. Indeed it was explained further down in the docum

Re: Crash as NSPersistentDocument creates its persistence stack

On Dec 23, 2008, at 4:44 PM, Jerry Krinock wrote: The NSPersistentDocument documentation doesn't give much detail -- "... an NSPersistenDocument creates its own ready-to-use persistence stack". I presume that it uses -mergedModelFromBundles:?

re: Crash as NSPersistentDocument creates its persistence stack

Jerry, That's pretty odd. Crashes in objc_msgSend are often memory management related, so you might start with NSZombieEnabled and MallocScribble, MallocPrescribble. malloc_history is also a great tool. - Ben ___ Cocoa-dev mailing list (Coco