Fred Kiefer wrote:
The corresponding real back trace is easy to get. Set a break point
on [NSException raise] and run AddressManager, try to add a new
person and you will get:
[...]
This could be either fixed in AddressView, by not setting the
string of a NSTextView to nil. Or we need to protect all calls to
the NSTextView in gui to ignore nil.
Not sure what Apple does here. Anybody out there with some time to
test this?
Apple reports an exception as well upon calling -setString: with a
nil argument:
2012-01-27 18:53:45.599 test[44382:903] An uncaught exception was
raised 2012-01-27 18:53:45.635 test[44382:903] *** -[NSTextView
replaceCharactersInRange:withString:]: nil NSString given.
Wolfgang