On 12-10-2014 9:13, Christoffer Holmstedt wrote:
Great work! Awesome to see this for Inkscape, static analysis is a must these days.

I feel the only way forward for our project is to use these tools.

I have never used Clang static analyzer, how good is it? a lot of false-positives?

I have not seen many false positives, but they are there. However, *all* false positives that I have seen in our codebase are the result of very very poor code design, and it takes a while to figure out that it is a false positive at all.
Clang's static analyzer is the best I have used and presents its reports in a nice HTML page that helps to find and fix the problem.
It's also easy to set up btw. (use scan-build)

-Johan



--
Christoffer Holmstedt

2014-10-12 9:03 GMT+02:00 Samuel Chase <samebchase@...400...>:
Hi Johan,

Wow. This looks like it could be really useful in the days to come!

Thanks for taking the time to set this up,

Samuel

On Thu, Oct 9, 2014 at 2:13 PM,  <jbc.engelen@...2592...> wrote:
> Hi all,
>   I have set up a daily build system that checks if trunk still builds (on Ubuntu) and, more importantly, runs clang's static analyzer using scan-build. You can find the results here:
> http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/
> After some clicking, you will find these interesting pages (links may become obsolete after a new build)
> http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/job/Inkscape_trunk_scan-build/Inkscape_trunk_scan-build_report/
> and
> http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/job/Inkscape%20trunk/7/warnings16Result/
>
> As you can see, there are still some nasty bugs in trunk. For example
> http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/job/Inkscape_trunk_scan-build/Inkscape_trunk_scan-build_report/report-b5ae8a.html#EndPath
>
> -Johan
>
> (currently I run Jenkins on free-tier EC2, but we are working on getting something more permanent. Expect a longer email with plans in the near future)
>