I wonder if the built in Analyzer in Xcode 3.1.4 makes it redundant to use LLVM/Clang Static Analyzer separately?
Please refer to the original article here: Finding memory leaks with the LLVM/Clang Static Analyzer
Thanks.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I wonder if the built in Analyzer in Xcode 3.1.4 makes it redundant to use LLVM/Clang Static Analyzer separately?
Please refer to the original article here: Finding memory leaks with the LLVM/Clang Static Analyzer
Thanks.
Correct. (assuming there’s a Build and Analyze option in 3.1.4, I thought it only made it to Snow Leopard).
Of course, the builds available directly from LLVM are newer than the ones with Xcode, so they probably fix some issues that may exist with the one currently packaged with Xcode. However, the static analyzer is pretty darn mature already, so you’re probably not missing out on much.