[Digikam-devel] Coverty Reports traces...

[Gilles Caulier]

About kipi-plugins reports, i sorted all traces by tools, for a better
analyse by developers :

https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation/repository/revisions/master/changes/project/reports/kipiplugins-3.0.0-0.14.rc.fc19.CovertyReport.log

It will be nice if each assigned tool will be review before 3.0.0 final
release planed on 6 February.

We have important trace about :

- DLNA export,
- RajceExport,
- VKontakteExport
- PrintImages
- ImgurExport
- PiwigoExport
- PhotoLayoutEditor
- VideoSlideshow
- RemoveRedEyes
- ExpoBlending
- FlickrExport


I can personalty manage RawConverter, DNGConverter, and all other few tools
reports, but i cannot do at all...

Please review code. Thanks in advance for your help.

Gilles


2013/1/24 Gilles Caulier <caulier.gilles at gmail.com>

> Hi all,
>
> Recently, I receive from Laurent Montel a set of traces about source code
> analys done with a tool named Coverty Report.
>
> http://www.coverity.com/
>
> This tool, which is not open-source have been aquired by Red Hat to check
> all implementation include will whole projects from the distro. RH has
> started to analyse KDE source code, and especially digiKam. I sorted huge
> trace to remove unsuitable parts and cut digiKam, kipi-plugins, and
> extralibs reports in separated files. All files are there :
>
>
> https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation/repository/revisions/master/show/project/reports
>
> Coverty check if all class members are initialized in constructors, if
> data or members are used before to be initialized, and if data are used
> after to be free from memory. The error list found in reports are listed in
> this PDF:
>
> http://www.coverity.com/library/pdf/Coverity_DS_CWMapping_cpp.pdf
>
> Where sometime reports are not really understable, i found some
> bugs discovered during source code analyse...
>
> I recommend highly to read all report and to fix source code relevant. The
> analyse have been done against digiKam 3.0.0-RC tarball source code.
>
> I already started to check digiKam source code and fixed some entries. I
> recommend to all developers to do the same quickly.
>
> Thanks in advance
>
> Gilles Caulier
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20130130/a8564ac1/attachment.html>