Re: Debugging Core Data unresolved keypath save error
Re: Debugging Core Data unresolved keypath save error
- Subject: Re: Debugging Core Data unresolved keypath save error
- From: Kevin Hoctor <email@hidden>
- Date: Tue, 20 Mar 2007 11:14:37 -0500
On Mar 20, 2007, at 11:03 AM, Chris Hanson wrote:
One way to get started debugging it is to set symbolic breakpoints
on the following:
objc_exception_throw
-[NSException raise]
That will let you stop in the debugger the instant the exception is
thrown, letting you debug a "live" system.
Thanks Chris, this gave me a bit more insight into what's going on:
#0 0x90a63365 in objc_exception_throw
#1 0x93cd01bb in -[NSSQLGenerator appendClause:forKeyPath:allowToMany:]
#2 0x93ccfca7 in -[NSSQLGenerator _preparePredicateExpression:]
#3 0x93ccfb16 in -[NSSQLGenerator prepareComparisonPredicate:]
#4 0x93ccb57e in -[NSSQLGenerator
prepareSelectStatementWithFetchRequest:]
#5 0x93ccb00f in -[NSSQLAdapter newSelectStatementWithFetchRequest:]
#6 0x93ccae40 in -[NSSQLChannel selectRowsWithFetchRequest:]
#7 0x93d04bc9 in -[NSSQLCore _newRowsForSelector:withArgument:andLimit:]
#8 0x93cca83b in -[NSSQLCore newRowsForFetchRequest:]
#9 0x93cca4ea in -[NSSQLCore objectsForFetchRequest:inContext:]
I'm still not sure why a save process is failing on building a
predicate. I'd love some feedback on this if anyone has experience
with this kind of error.
Kevin
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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