Hello All,
I am using NSMutableSet quite extensively in my app mostly just adding
items to it and reading them (almost never removing). However sometimes it
crashes under very interesting conditions. I can't reliable recreate the issue
but sometimes I get a 'attempted to insert nil' exception when FILTERING the
set using a predicate, if I breakpoint at this exception and print the set
description I see that it has many valid objects but also a bunch of nil (null)
objects which doesn't make any sense since I can't insert nil objects to the
set in the first place!
I can't think of any scenario where I can insert nil objects to the set
or insert a valid object which would then point nil. My app is multi-threaded
and the set is accessed in @sychronized blocks from many threads all the time.
Has anyone had a similar problem? am I missing something? is it a bug
with the foundation object?
Thanks for any insight.
Regards,
Alejandro RodrÃguez_______________________________________________
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
