The technique I typically use to debug these types of log messages is
a breakpoint on NSLog. If that isn't hit, you could try a breakpoint
on write. After you hit the breakpoint, verify that it's for the log
message you're trying to debug, and then use the backtrace to get an
idea of what exactly is causing the log message.
Jon Hess
On May 27, 2009, at 5:15 PM, Graham Cox wrote:
I'm getting this in the log when I open the "Customize Toolbar" sheet:
-[NSConcreteAttributedString initWithString:] called with nil
string argument. This has undefined behavior and will raise an
exception in post-Leopard linked apps. This warning is displayed
only once.
Is this a bug in the frameworks or in my code? I tried setting a
symbolic breakpoint on this but it doesn't fire at all, though if it
did I'm not sure how I'd make it conditional on the string being nil
as there are no debugging symbols.
It would be preferable if this did throw an exception, at least it
could be tracked down more easily.
--Graham
_______________________________________________
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/jhess%40apple.com
This email sent to jh...@apple.com
_______________________________________________
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 arch...@mail-archive.com
