On 20 March 2016 at 20:53, Jaroslaw Staniek <stan...@kde.org> wrote: > > Hi! > Volunteers interested in simple works such as fixing uninitialized > variables for Kexi and related code feel free to respond. We're using > Coverity static analysis tools so in addition to having your name listed in > the hall of fame, it's possible to learn about a tool known in the industry. >
Update: Results are very positive so far. - Many fixes for Kexi 2 & 3 are already committed: https://scan.coverity.com/projects/kexi. - We've found no serious bugs and even not so many moderate bugs in the sister project KDb, that's probably because extensive autotesting exists for it and also valgrind was used frequently: https://scan.coverity.com/projects/kdb - Checks for further sister projects are submitted, expected within a week: https://scan.coverity.com/projects/kreport, https://scan.coverity.com/projects/kproperty -Interesting false positive for any Qt/KDE project is related to d-pointers. Basically attributes of Private* classes are not initialized in these classes directly but in the main class, e.g. d->foo = new QPushButton; So we have to mark these cases as false positives by hand (only once, not per build). <http://www.linkedin.com/in/jstaniek> > If you're interested in helping out (probably soon for KReport and KProperty), please respond. The Coverity Scan is in heavy use worldwide so we're repeating checks mostly after nontrivial changes, not after every commit. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
_______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
