From kde-imaging Wed Jan 30 14:33:00 2013 From: Gilles Caulier Date: Wed, 30 Jan 2013 14:33:00 +0000 To: kde-imaging Subject: Re: [Kde-imaging] Coverty Reports traces... Message-Id: X-MARC-Message: https://marc.info/?l=kde-imaging&m=135955643703398 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============8197898309530526969==" --===============8197898309530526969== Content-Type: multipart/alternative; boundary=089e013d16344dd4b204d4826475 --089e013d16344dd4b204d4826475 Content-Type: text/plain; charset=ISO-8859-1 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 > 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 > > --089e013d16344dd4b204d4826475 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
About kipi-plugins reports, i sorted all traces by tools, = for a better analyse by=A0developers=A0:

https://projects.kde.org/projects/ext= ragear/graphics/digikam/digikam-software-compilation/repository/revisions/m= aster/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=A0February.

We have important trace about :

- DLNA export,
- RajceExport,
- VKontakteExport
- PrintImages
- Imgur= Export
- PiwigoExport
- PhotoLayoutEditor
- VideoSlideshow
- RemoveRedEyes
- ExpoBlending
- FlickrExport


I can=A0personalty=A0manage RawConverter, DNG= Converter, and all other few tools reports, but i cannot do at all...

Please review code. Thanks in advance for y= our help.

Gilles


2013/1/24 Gilles Caulie= r <caulier.gilles@gmail.com>
Hi all,

=
Recently, I receive from Laurent Montel a set of traces about so= urce code analys done with a tool named Coverty Report.=A0


This tool, which is not open-source have = been aquired by Red Hat to check all implementation include will whole proj= ects from the distro. RH has started to analyse KDE source code, and especi= ally digiKam. I sorted huge trace to remove unsuitable parts and cut digiKa= m, kipi-plugins, and extralibs reports in separated files. All files are th= ere :

https://projects.kde.org/projects/extrage= ar/graphics/digikam/digikam-software-compilation/repository/revisions/maste= r/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 rep= orts are listed in this PDF:


Where sometime reports are not really under= stable, i found some bugs=A0discovered=A0during source code=A0analyse...

I recommend=A0highly=A0to 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 fixe= d some entries. I recommend to all=A0developers=A0to do the same quickly.

Thanks in advance

Gilles Caulier


--089e013d16344dd4b204d4826475-- --===============8197898309530526969== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kde-imaging mailing list Kde-imaging@kde.org https://mail.kde.org/mailman/listinfo/kde-imaging --===============8197898309530526969==--