ansaurus

Question

What do these errors in the XCode Debugger Mean?

Answer 1

+2 A:

It would appear you've tried to filter based on a key called 'group' in an object that doesn't have a key called group.

The rest is a stack trace.

Nick Veys 2009-06-30 18:05:55

Thanks, Is a stack trace ok or does it need to be fixed? Also what does it mean by KeyPath because when i created the bindings that was what it wanted to filter automatically even though there is nothing called that?

Joshua 2009-06-30 18:09:13

The object/Array is connected to Core Data and there is an entity called Group, So shouldn't it work? It may be a bit harder to make it work also because I am also using a NSTreeController with a NSOutlineView to display the Data.

Joshua 2009-06-30 18:13:09

When you fix the first error, the stack trace will go away. The stack trace is intended to help you track down what went wrong. It si not inherently bad, it is just a road map to the bad this (the actual exception).

MystikSpiral 2009-06-30 18:14:03

Ok, I've got rid of the error, but it doesn't filter my NSOutlineView.

Joshua 2009-06-30 18:17:22

@MystikSpiral Thanks!

Joshua 2009-06-30 18:17:55

Stack tracebacks and diagnostics are generally considered untoward behavior, or can be considered evidence of more serious underlying problems or programming instability.KVC reading: http://developer.apple.com/documentation/Cocoa/Conceptual/KeyValueCoding/Concepts/BasicPrinciples.htmlDoes this need to be fixed? That's entirely up to you and to whomever is going to be using this, and up to whether the program works or not, and whether or not you care if there are visible bugs here.

Stephen Hoffman 2009-06-30 18:20:24

@Stepehn Thanks to you also!

Joshua 2009-06-30 18:22:19

"the entity group is not key value coding-compliant for the key keyPath"The key that's failing isn't "group", it's "keyPath".

Tom Dalling 2009-06-30 22:40:44

Ok, I've got rid of the error now by changing what it filters to what it should filter, but it doesn't actually filter my NSOutlineView.

Joshua 2009-07-01 05:26:33

Joshua: A stack trace tells you what was happening when the exception occurred, by tracing the call stack (x called y, y called z, z called a, etc.). To use it, convert the addresses to hex, then pass them to dwarfdump along with the path to your .dSYM bundle. (See man dwarfdump for details.)

Peter Hosey 2009-07-01 07:15:31

Answer 2

+1 A:

I see the first occurrence most often when i have bound a control to an IBOutlet via Interface Builder and then removed/renamed the IBOutlet in the underlying class. Check on the Connections tab for File's Owner in IB and see that there are not any odd connections that need to be cleaned up.

The second is the cryptic stack trace used on the Console when you hit an exception. It is actually a list of pointer addresses allowing you to trace the execution path. There is a ton you can do on the console once you get comfortable there. I got a great headstart on this (and MUCH MORE) on Cocoa With Love: http://cocoawithlove.com/2008/10/debugging-tips-for-objective-c.html

Good Luck!

MystikSpiral 2009-06-30 18:12:30

There are some great tips there, thanks for the link.

Joshua 2009-06-30 18:24:46

ansaurus

tags:

views:

answers:

What do these errors in the XCode Debugger Mean?

related questions