Re: Debugging the dreaded "CoreData could not fulfill a fault...."

2009-02-28 Thread Ben Trumbull
>cat ~/.gdbinit future-break objc_exception_throw future-break +[NSError errorWithDomain:code:userInfo:] future-break handleFailureInMethod:object:file:lineNumber:description: future-break handleFailureInFunction:file:lineNumber:description: future-break malloc_printf - Ben

Re: Debugging the dreaded "CoreData could not fulfill a fault...."

2009-02-27 Thread Jerry Krinock
I believe I've found the cause of this. For future reference, the successful troubleshoot was logging at the beginning and end of any methods which might be invoked automatically to update views, such as -reloadData, -menuNeedsUpdate, - validateMenuItem, etc. In my case, it looks like the

Re: Debugging the dreaded "CoreData could not fulfill a fault...."

2009-02-27 Thread Jerry Krinock
On 2009 Feb 27, at 16:21, Jesper Storm Bache wrote: If that is the only message you see in the console, then you can try to break on "asl_send". Thanks, Jesper. Seemed like a great idea, but unfortunately it looks like the the root causer is not in the call stack... #0 0x939822ce i

RE: Debugging the dreaded "CoreData could not fulfill a fault...."

2009-02-27 Thread Jesper Storm Bache
If that is the only message you see in the console, then you can try to break on "asl_send". Jesper Storm Bache From: cocoa-dev-bounces+jsbache=adobe@lists.apple.com [cocoa-dev-bounces+jsbache=adobe@lists.apple.com] On Behalf Of Jerry Krinock [je