https://bugs.kde.org/show_bug.cgi?id=364231
caulier.gil...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|REPORTED |RESOLVED
Version Fixed In| |7.1.0
--- Comment #11 from caulier.gil...@gmail.com ---
Hi Max,
In my office where is maintain a C/C++/qt framework based with more than 1.2 M
of code lines, i deployed a CI with 3 static analysers : cppcheck, Krazy, and
clang-scan. I cannot use Coverity as code is closed.
For digiKam i used the same static analysers + Coverity. We discover plenty of
bugs, more and less important and a lots of C++11 improvements to include for
the future.
You can found my bash scripts to run static analyzers here. They generate web
page with reports:
https://invent.kde.org/graphics/digikam/-/tree/master/project/reports
There is another analyser that you can use in your library : asan. But this
will require to write plenty of unit tests to check all use cases. Alternaitve
is to use run-time memory check know as Dr valgrind
cppcheck.sourceforge.net
https://github.com/Krazy-collection/krazy
https://clang-analyzer.llvm.org/scan-build.html
https://github.com/google/sanitizers/wiki/AddressSanitizer
https://valgrind.org/
I close this file now as libjasper maintenance revival well and is suitable for
the future.
Thanks for you great job.
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
