[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-imaging
Subject: Re: [Kde-imaging] Coverty Reports traces...
From: Gilles Caulier <caulier.gilles () gmail ! com>
Date: 2013-01-30 14:33:00
Message-ID: CAHFG6sF90g6FBS2sG1wTRa4bGTgTcfUKkO_SEA-gAx3i3yTkWQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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/revis \
ions/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@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
>
>
[Attachment #5 (text/html)]
<div dir="ltr">About kipi-plugins reports, i sorted all traces by tools, for a better analyse by \
developers :<div><br></div><div><a \
href="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">https://projec \
ts.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</a><br>
</div><div><br></div><div style>It will be nice if each assigned tool will be review before 3.0.0 final \
release planed on 6 February.</div><div style><br></div><div style>We have important trace about \
:</div><div style><br>
</div><div style>- DLNA export,</div><div style>- RajceExport,</div><div style>- \
VKontakteExport</div><div style>- PrintImages</div><div style>- ImgurExport</div><div style>- \
PiwigoExport</div><div style>- PhotoLayoutEditor</div>
<div style>- VideoSlideshow</div><div style>- RemoveRedEyes</div><div style>- ExpoBlending</div><div \
style>- FlickrExport</div><div style><br></div><div style><br></div><div style>I can personalty manage \
RawConverter, DNGConverter, and all other few tools reports, but i cannot do at all...</div>
<div style><br></div><div style>Please review code. Thanks in advance for your help.</div><div \
style><br></div><div style>Gilles</div></div><div class="gmail_extra"><br><br><div \
class="gmail_quote">2013/1/24 Gilles Caulier <span dir="ltr"><<a \
href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div>Hi all,</div><div><br></div><div>Recently, I receive from \
Laurent Montel a set of traces about source code analys done with a tool named Coverty Report. </div>
<div><br></div><div>
<a href="http://www.coverity.com/" \
target="_blank">http://www.coverity.com/</a></div><div><br></div><div>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-compilation/repository/revisions/master/show/project/reports" \
target="_blank">https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation/repository/revisions/master/show/project/reports</a><br>
<div><br></div><div><div>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>
<br></div><div><a href="http://www.coverity.com/library/pdf/Coverity_DS_CWMapping_cpp.pdf" \
style="font-family:arial,sans-serif;font-size:12.800000190734863px" \
target="_blank">http://www.coverity.com/library/pdf/Coverity_DS_CWMapping_cpp.pdf</a><br>
</div></div><div><br></div><div>Where sometime reports are not really understable, i found some bugs \
discovered during source code analyse...</div><div><br></div><div>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>I already started to check digiKam source code and fixed some entries. I recommend to \
all developers to do the same quickly.</div><div><br></div><div>Thanks in advance</div><span \
class="HOEnZb"><font color="#888888"><div>
<br></div><div>Gilles Caulier</div><div><br></div></font></span></div>
</blockquote></div><br></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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic