I _strongly_ suggest that you (at least temporarily) use the LLVM/
CLANG compilers in XCode, and use the "build and analyze" option that
is then available. By the time you have fixed every issue that CLANG
finds, I suspect that 90% of your crashes will have evaporated, as
well as quite a few issues that you haven't discovered yet. This is
going to be much more productive than trying to analyze stack crawls.
The static analyzer is particularly adept at finding retain-release
issues and obscure uninitialized variable issues -- both of which are
notorious for causing difficult-to-pin-down misbehaviors.
AFAIK the only consistent false positive in the current version is
that it blindly assumes that the {NSData,NSString} methods with
'NoCopy' in the name are returning a retained object. If you don't
happen to be using any of these, (or any macros that hide relevant
code, because the analyzer appears to operate only on unexpanded code)
you should be golden.
_______________________________________________
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
