I maintain an Objective-C project which uses a C library that implements a garbage-collected scripting environment. In several cases, I need to put a retained Objective-C object in the private field o
I am doing the final touch ups on an app and I am getting rid of every compiler/开发者_StackOverflow中文版analyzer warning.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepti开发者_开发问答ng answers.
Having just upgraded to iOS 4.1 (Xcode 3.2.4) I am getting warnings when using the static analyser that I don\'t think I was previously getting when using 3.2.3
I’m using Xcode 3.2.4 and have setup the Clang Static Analyser feature to use a newer build of the binary, as detailed here: http://clang-analyzer.llvm.org/xcode.html
I have upgraded my XCode to versio 3.2.3 to support iOS4 on my iphone project. using the static analyser I checked for memory management problems.
I have a function that is creating a variable, but not deallocating it.It passes this object on with a message to another function that deals with the memory management.
I am analyzing Objective-C iPhone project with LLVM/Clang static analyzer. I keep getting two reported bugs, but I am pretty sure that the code is correct.
I\'ve used the Clang Static Analyzer from the command line before. I wanted to try Xcode\'s built-in version via Build & Analyze. I never get any negative results even though i specially prepared
It doesn\'t care about this: NSString* leaker() { return [[NSString alloc] init]; } I thought it would have been smart enough to check if any code paths could call that function without releasing