Re: Debugging the dreaded "CoreData could not fulfill a fault...."
Re: Debugging the dreaded "CoreData could not fulfill a fault...."
- Subject: Re: Debugging the dreaded "CoreData could not fulfill a fault...."
- From: Jerry Krinock <email@hidden>
- Date: Fri, 27 Feb 2009 17:40:38 -0800
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 in asl_send
#1 0x907bd574 in __CFLogCString
#2 0x907bda4b in _CFLogvEx
#3 0x955895fe in NSLogv
#4 0x955e8a0b in NSLog
#5 0x969d996c in _NSDefaultTopLevelErrorHandler
#6 0x967cf564 in -[NSApplication run]
#7 0x9679c8a4 in NSApplicationMain
#8 0x000ae255 in main at DemoApp-Main.m:22
That _NSDefaultTopLevelErrorHandler must be in the run loop, breaks
into logging when it sees a flag of some kind. I need to know what
set the flag.
So, it's back to guessing unless someone has another idea.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden