On Mar 10, 2010, at 23:31:02, David Dunham wrote:
Given that CF does no error checking, it's more likely a case of bad
data sent in.
Here's our part of that call stack:
plistData = [NSPropertyListSerialization dataFromPropertyList:regDict
format:NSPropertyListBinaryFormat_v1_0
errorDescription:&error];
regDict is checked for nil 21 lines earlier. The format constant is
definitely valid there. &<local-variable> is a pointer that will be
valid for the entire duration of the stack frame; it's definitely
valid here. (It would be a different story if we'd, say, returned that
pointer to -_launchGrowlIfInstalled…'s caller.)
There are two remaining possibilities:
1. regDict is not a dictionary or any other plist object. I actually
don't know what would happen in this case. It'd certainly be an
application mistake, as the object would have to come from the
delegate's -registrationDictionaryForGrowl method.
2. regDict is a dead object. This, too, would be the application's
fault.
--
You received this message because you are subscribed to the Google Groups "Growl
Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/growldiscuss?hl=en.
