source code static analyze with Clang "scan-build"...

Gilles Caulier caulier.gilles at gmail.com
Fri May 4 16:48:18 BST 2018


Hi all,

You must know that we parse norally all source code with Coverity Scan
service and fix step by step the issues detected by the static analyzer.

Since January, git/master cannot be processed by Coverity. The build is
complete, but the report is never commited and is send in somewhere in
/dev/nulll (:=)))...

Coverity Scan service was acquired by a new company in 2018, and i suspect
a side effect to commit report to the remote server. I contacted the
Coverity team, who respond that investiguation are under progress, please
wait.

So, i finally try to found a new solution to parse week by week all source
code to review by another static analyzer. I tried Clang one, and reports
are really excellent. I written a script in project/reports/, but it's not
yet perfect.

The first report that clang generate is really interesting. I shared the
files (web pages) in this archive :

https://drive.google.com/open?id=1EKr9vAMZFZ8-UDOXXIrzKdlt5G8ClVD1

Please take a look and feel free to apply patches is necessary.

I will try to finalize the script while this week end to be able to run the
analyzer locally.

Best

Gilles Caulier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20180504/ffad3689/attachment.html>


More information about the Digikam-devel mailing list