[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-imaging
Subject:    [Kde-imaging] Coverty Reports traces...
From:       Gilles Caulier <caulier.gilles () gmail ! com>
Date:       2013-01-24 17:06:44
Message-ID: CAHFG6sFy-bK6_OgH9Q+p1vmPm6OFuU69+Nb-ZLR-cTdPNvm0LQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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


[Attachment #5 (text/html)]

<div dir="ltr"><div style>Hi all,</div><div style><br></div><div style>Recently, I receive from Laurent \
Montel a set of traces about source code analys done with a tool named Coverty Report. </div><div \
style><br></div><div style>

<a href="http://www.coverity.com/">http://www.coverity.com/</a></div><div style><br></div><div style>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 :</div>

<div><br></div><a href="https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-comp \
ilation/repository/revisions/master/show/project/reports">https://projects.kde.org/projects/extragear/grap \
hics/digikam/digikam-software-compilation/repository/revisions/master/show/project/reports</a><br>

<div><br></div><div><div style>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:<br class="">

<br></div><div><a href="http://www.coverity.com/library/pdf/Coverity_DS_CWMapping_cpp.pdf" \
target="_blank" style="font-family:arial,sans-serif;font-size:12.800000190734863px">http://www.coverity.com/library/pdf/Coverity_DS_CWMapping_cpp.pdf</a><br>


</div></div><div><br></div><div style>Where sometime reports are not really understable, i found some \
bugs discovered during source code analyse...</div><div style><br></div><div style>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.</div>

<div><br></div><div style>I already started to check digiKam source code and fixed some entries. I \
recommend to all developers to do the same quickly.</div><div style><br></div><div style>Thanks in \
advance</div><div style>

<br></div><div style>Gilles Caulier</div><div style><br></div></div>



_______________________________________________
Kde-imaging mailing list
Kde-imaging@kde.org
https://mail.kde.org/mailman/listinfo/kde-imaging


[prev in list] [next in list] [prev in thread] [next in thread]