Comments on: Tutorial: How To Static Analyze Your Objective-C Code Using the Clang Static Analyzer Tool

By: Bruce

Bruce — Wed, 19 May 2010 16:22:06 +0000

Very very good tutorial, short and complete .

Well done mate, Well done.

By: houman

houman — Mon, 28 Dec 2009 02:59:43 +0000

Very very good tutorial, short and complete .

Well done mate, Well done.

By: Eric

Eric — Mon, 30 Mar 2009 10:46:02 +0000

Well if you are familiar with the LLVM compiler within XCode, it adds this support to the command line, specifically for clang which is simply a replacement for GCC. Clang has tons of uses though(http://clang.llvm.org/features.html), but benefits… none really unless you’re a geek like me like to try all the cool new tools.

By: Dong

Dong — Mon, 30 Mar 2009 07:49:44 +0000

Hi Eric, what’s the benefit of adding the first two steps about (install LLVM/Clang (Optional))? Thanks.

By: Joel Norvell

Joel Norvell — Sun, 04 Jan 2009 03:17:22 +0000

Eric,
I finally figured out how to edit /etc/profile and was able to run the analyzer on my project. I’m most grateful to you for this tutorial!
Joel

By: Joel Norvell

Joel Norvell — Sat, 03 Jan 2009 06:35:49 +0000

Eric,

Thanks for doing this.

Although I “washed out” at nano and had some other questions about what I was doing (I couldn’t see the directory when I created it in /usr/bin so I created it in /Developer/usr/bin), I’m hopeful that I can obtain some guidance at the next NSCoder Night because I really need to use the code analyzer!

By: Manish Srivastava

Manish Srivastava — Fri, 28 Nov 2008 14:34:12 +0000

Thanks, Eric
Really you put awesome presentation. Its definitely help lots of developer.

By: Ted Kremenek

Ted Kremenek — Sun, 28 Sep 2008 04:31:25 +0000

Thanks Eric for putting together such a great tutorial!

For those using the tutorial, the semi-regular builds we do of the analyzer for Mac OS X (other platforms can compile from the sources in SVN) actually contains a built copy of the ‘clang’ executable. scan-build/ccc-analyzer will first look for ‘clang’ in the same directory that they are installed in; if you decide to build your copy of ‘clang’ from SVN sources make sure you remove the prebuilt one.

Alternatively, one can just use scan-build and its related tools directly from SVN; they are just not as conveniently packaged, and we don’t have a “make install” or similar option yet in SVN for the static analyzer. The reason for this is that the bundling of commands and resources is rapidly changing, and the clang repository itself includes not only the static analyzer, but they clang frontend, some code rewriter libraries, etc.

One advantage of using the semi-regular builds published at clang.llvm.org is that we tag the repository for “release” builds after we have made a certain number of changes to the repository that we think are “stable” enough for general release. This is still beta-quality software, but we do try and keep the builds generally useable.