[cfe-dev] scan-build in python

[Anna Zaks]

It would be interesting to see this project live! Developing a system for tracking issues over time and managing the bug reports is important for any static analyzer and we have been thinking about it for a while. clang/utils/analyzer/CmpRuns.py is a baby step in that direction (not sure if Alexey uses it or not).

What is the main reason this is done on a forked clang? Is it the time constraints that would be imposed by code review?

Cheers,
Anna.

> On Aug 26, 2014, at 10:13 AM, Sylvestre Ledru <sylvestre at debian.org> wrote:
> 
> Hello,
> 
> By the way, Alexey, during his gsoc, has made a lot of great progress.
> We have now a web interface based on clang/scan-build. It allows tracking of the history, mark of false positives and other
> cool stuff. 
> 
> It needs some documentations and polish but if you are interested to test, you can have a look here:
> https://github.com/alexey-klimov/clang/ <https://github.com/alexey-klimov/clang/>
> He addressed the database issue by using an abstraction layer (sqlalchemy). Maybe it could be interesting to use the same base.
> 
> Documentation is available here:
> https://github.com/alexey-klimov/clang/tree/scan-build_tracking_platform/tools/tracking-platform/example <https://github.com/alexey-klimov/clang/tree/scan-build_tracking_platform/tools/tracking-platform/example>
> 
> I will try to deploy a proof of concept with LLVM/Clang like I am doing with:
> http://llvm.org/reports/scan-build/ <http://llvm.org/reports/scan-build/>
> 
> Cheers,
> Sylvestre

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20140827/ab81c42d/attachment.html>