[cfe-dev] scan-build in python

[Jordan Rose]

This is the right list for analyzer questions. Ted Kremenek, Anna Zaks, and I are the primary maintainers. What in particular is broken in ccc-analyze / scan-build?

Also, being able to run the analyzer against a compilation database seems like a good feature. I think the auxiliary "clang-check" executable can already do this with its -analyze option, though I haven't tried it, but it doesn't allow for much customization of the output like scan-build does. Still, it could give you a place to start.

> 	For example, to run clang-check on all files in a subtree of the
> 	source tree, use:
> 
> 	  find path/in/subtree -name '*.cpp'|xargs clang-check
> 
> 	or using a specific build path:
> 
> 	  find path/in/subtree -name '*.cpp'|xargs clang-check -p build/path

Jordan



On Oct 21, 2013, at 3:47 , Laszlo Nagy <rizsotto.mailinglist at gmail.com> wrote:

> hi there,
> 
> started to write a python script around Clang's static analyzer.
> mainly because found difficult to use the `scan-build` script. wanted
> to run against a compilation database instead of intercept the
> compiler calls. but would like to preserve the current usage as
> well... then at the same time, saw this page
> <http://clang-analyzer.llvm.org/open_projects.html> which suggest the
> rewrite as well. so, it might be a perfect match! ;)
> 
> and as i try to copy the functionality of the `ccc-analyze` and
> `scan-build` scripts, discovered few minor bugs. (or they are not
> bugs, and i'm the one who can't read perl well.)
> 
> now i'm looking for a person i can ask about these scripts.
> 
> regards,
> Laszlo
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev