Fixing logged error that doesn't throw exception
Fixing logged error that doesn't throw exception
- Subject: Fixing logged error that doesn't throw exception
- From: Tristan Celder <email@hidden>
- Date: Thu, 25 Jun 2009 10:34:41 +0100
Hi,
I'm extremely new to Cocoa programming but have come across a problem
where I am getting a [NSConcreteAttributedString initWithString:]
called with nil string argument. pop up in my console. I have had it
once before and managed to track it down to a NumberFormatter with no
symbols set for nil/null values. This problem was the cause of a far
more serious problem which was a very bizarre error which breaks my
core data bindings for any table view displaying exactly one row of an
attribute fetched via a relationship when a document is reopened after
save.
Unfortunately the console warnings have begun popping up again, and
this time I have absolutely no idea where/who/what could be causing
them in my interface. (It's only when I do a clean build that they
show up in the first place). So... what I would really like to know is
how I can find the source of these messages. A previous post I dug up,
simply mentions that one can "test the location on the stack which
holds the parameter." which can be done using the syntax "*(id*)($ebp
+ 16)".
Now, as I'm new to cocoa development (And C in general), my knowledge
of gdb is limited. How would I set this breakpoint from xcode?
Thank you in advance, T.
_______________________________________________
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