>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
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
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
y
Krinock [je...@ieee.org]
Sent: Friday, February 27, 2009 4:11 PM
To: Cocoa Developers
Subject: Debugging the dreaded "CoreData could not fulfill a fault"
For the last hour or so I've been debugging a "CoreData could not
fulfill a fault..." log message.
The error tell
For the last hour or so I've been debugging a "CoreData could not
fulfill a fault..." log message.
The error tells me ^what^ object is involved, but not ^why^ it thinks
it needs to fulfill the fault. I've checked through everything I can
think of, and all Delete Rules involving this object
