Fwd: kdepimlibs Coverity Scan Report, Oct 14 2014

Gilles Caulier caulier.gilles at gmail.com
Thu Oct 16 08:53:52 BST 2014


Just a workflow question : why to export Coverity report to CSV where
you can send automatically a mail to devel mailing list when scan is
complete, with a a list of new defect found in code.

I use Coverity since more than one year with whole digiKam code, and
we have already fixed more than 500 entries detected. The Coverity web
interface is really more suitable than a export to CSV. Defect are
very well explained in source context, with all conditions used to
check implementation.

The only constrain is to have an account for each contributors who
will fixed entries.

After one year to use this tool, the feedback is really excellent,
especially to check new code from students.


Gilles Caulier

2014-10-14 14:30 GMT+02:00 Allen Winter <allen.d.winter at gmail.com>:
> Howdy,
> Attached is the Coverity Scan report for kdepimlibs 4.14 as of today.
> You might feel like fixing some of the issues.
> Let me know if you find false positives or stuff we can ignore (like in test programs).

More information about the kde-core-devel mailing list