The 'leaks' tool has identified several NSString objects that my app is leaking. But neither 'leaks' nor Instruments > Leaks identifies the responsible frame in my code. The 'leaks' tool gives me the string value, but I still need more clues to find it in my code.
This string appears to be the 'path' of a file:// NSURL, which is also leaking, so I surmise it is actually the NSURL which is leaking. Does anyone know a method in NSURL or NSString in which I could set a breakpoint with a condition to trigger whenever its path or string gets set to a certain value? Thanks, Jerry I've tried the following Symbolic Breakpoints… -[NSString initWithString:] -[NSURL initWithScheme:host:path] -[__NSCFString init] with *no* breakpoint conditions, but, to my surprise, I get no breaks at all! Maybe Apple has optimized these methods so much that they only really exist in the documentation nowadays? _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
