On Mar 18, 2008, at 00:33, Steve Cronin wrote:
On Leopard in the 'processPendingChanges' invocation I get the
following:
0 0x900ef0f4 in ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___
#1 0x93d680fb in objc_exception_throw
#2 0x9649a2a5 in -
[NSManagedObjectContext(_NSInternalChangeProcessing)
_processRecentChanges:]
#3 0x964adbea in -[NSManagedObjectContext processPendingChanges]
#4 0x0002032e in -[AppDelegate updateCoreData] at AppDelegate.m:700
BTW: I also get a similar error if, during the loading, I try to
get a 'count' using a FetchTemplate with a null predicate (works on
Tiger)
It appears the fetch also causes a 'processRecentChanges)
Don't neglect the obvious. In general, the frameworks log an error
message when they throw an exception. You don't say if you checked the
log for messages.
Is there a custom uncaught exception handler at work here? If so, it
might be that it's terminating the application before the message is
actually logged, since logging seems to be asynchronous with
exceptions in Leopard. (Setting a breakpoint on objc_exception_throw
almost always enters the debugger before the corresponding message is
logged in the console window.)
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
