Fedora Static Analysis Special Interest Group (SIG)

(Note that this SIG is merely tentative for now)

Goal and Scope

TBD

dmalcolm is interested in making it easy to run static code analysis tools on all of Fedora, and having a sane system for getting useful information from the firehose of data that doing so is likely to generate. See http://lists.fedoraproject.org/pipermail/devel/2012-December/175232.html

See also the Formal Methods SIG with which there's clearly an overlap.

TBD

TBD; Fedora's main devel list for now

TODO

gcc - arguably we should pay more attention to the compiler warnings that gcc already generates: sometimes it's correctly pointing out a bug.
clang static analyzer (in Fedora as "clang-analyzer" subpackage of "llvm")
cpychecker (part of gcc-python-plugin)
flawfinder (that page has a great list of links to other static analysis tools)
cppcheck Cppcheck is a static analysis tool for C/C++ code.
sparse - a Semantic Parser for C, primarily used by kernel developers.

dmalcolm: for Fedora 17 I attempted to run all of the Python C extension code in Fedora through my cpychecker cpychecker tool. I want to repeat this analysis, but this time to capture the results in a database.

This is 4 parts:

IN PROGRESS: firehose: an interchange format so we can capture results from all static analyzers in a consistent format. This consists of:
- an XML serialization format (with a RELAX NG schema)
- a Python module for in-memory creation/manipulation
- parsers for converting analysis results into the common format:
  - DONE: gcc warnings
  - DONE: cppcheck warnings (v2 of its XML output format)
  - DONE: clang-static-analyzer (the .plist output format)
  - IN PROGRESS: cpychecker warnings (patching cpychecker so that internally it uses the above python API's classes)
  - others?
- handle analyzer failures (where an analyzer choked and all or part of a source file failed; nice to capture where the failure happened).
TODO: "mock-with-analysis" (need better name?): a way of doing a mock rebuild of a src.rpm with minimal effect on the main build, whilst injects a side-effect of running static analyzers on each c/c++ file compiled (other languages?), and drops firehose XML files into the chroot as results as it goes, so that they can be slurped into a database
TODO: "firehose-ui": a db and web UI for summarizing reviewing results from many analyzers across many packages, with nice workflows
TODO: gluing all of the above together and deploying it.
- having a team that comes up with filters that achieve a decent signal:noise ratio, so that J Random package maintainer doesn't have to wade through so much noise