MDN wants to learn about developers like you:

Clang static analysis

Great news: If you want to build with the Mozilla Clang plug-in (located in /build/clang-plugin and associated with MOZ_CLANG_PLUGIN and the attributes in /mfbt/Attributes.h), it's much easier than this: just add --enable-clang-plugin to your mozconfig!

Clang has a built-in static analyzer. The gist is you add a wrapper around the compiler which directs all static analysis results to a common location. At the end of a build, these reports are aggregated into a report document showing all the potential issues.

These instructions will only work where Mozilla already compiles with Clang. At the time this was written, Mac OS X and GNU/Linux has strong support.
Please note that most of the static analyzer effort on clang are mostly done in clang-tidy as checkers are much easier to write.

Ideally, the static analysis would be performed independently from compilation. See bug 663442 to track a work around that facilitates easier static analysis.

Installing Clang

The first step to running static analysis is installing Clang. Clang is now shipped on most of the GNU/Linux distributions but also shipped with Xcode as the default compiler.

Configuring the build environment

Once you have your Clang build in place, you'll need to set up tools to use it.
A full working .mozconfig for the desktop browser is:

. $topsrcdir/browser/config/mozconfig
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-ff-dbg

ac_add_options --enable-debug

Attempts to use ccache will likely result in failure to compile. It is also necessary to avoid optimized builds, as these will modify macros which will result in many false positives.

At this point, your Mozilla build environment should be configured to compile via the Clang static analyzer!

Performing scanning builds

It is not enough to simply start the build like normal. Instead, you need to run the build through a Clang utility script which will keep track of all produced analysis and consolidate it automatically.

That script is scan-build. You can find it in $clang_source/tools/scan-build/scan-build.

Try running your build through scan-build:

$ cd /path/to/mozilla/source

# Blow away your object directory because incremental builds don't make sense
$ rm -rf obj-dir

# To start the build:
scan-build --show-description ./mach build -v

# The above should execute without any errors. However, it should take longer than
# normal because all compilation will be executing through Clang's static analyzer,
# which adds overhead.

If things are working properly, you should see a bunch of console spew, just like any build.

The first time you run scan-build, CTRL+C after a few files are compiled. You should see output like:

scan-build: 3 bugs found.
scan-build: Run 'scan-view /Users/gps/tmp/mcsb/2011-12-15-3' to examine bug reports.

If you see a message like:

scan-build: Removing directory '/var/folders/s2/zc78dpsx2rz6cpc_21r9g5hr0000gn/T/scan-build-2011-12-15-1' because it contains no reports.

either no static analysis results were available yet or your environment is not configured properly.

By default, scan-build writes results to a folder in a pseudo-temporary location. You can control where results go by passing the -o /path/to/output arguments to scan-build.

You may also want to run scan-build --help to see all the options available. It is possible to selectively enable and disable individual analyzers, for example.

Analyzing the output

Once the build has completed, scan-build will produce a report summarizing all the findings. This is called index.html in the output directory. You can run scan-view (from $clang_source/tools/scan-view/scan-view) as scan-build's output suggests; this merely fires up a local HTTP server. Or you should be able to open the index.html directly with your browser.

False positives

There are currently many false positives in the static analyzer. A lot of these are due to the analyzer having difficulties following the relatively complicated error handling in various preprocessor macros. For example, most of our ASSERT() macros call other functions which themselves call assert() or do something else.

In the long term, we should add a set of macros enabled via #ifdef which provide simple macros understandable by the static analyzer. There are also some pragmas and compiler extensions we can investigate using to silence warnings.

See also

Document Tags and Contributors

 Contributors to this page: sylvestre, jorendorff-moz, bbouvier, Ehsan, Sheppy, gps
 Last updated by: sylvestre,