Which tools for static code analysis do you use?
-
wrote on 14 Dec 2010, 09:05 last edited by
Hi fellow devs,
do you do static code analysis for your projects?
If so, which tools do you use? (OpenSource, Commercial...)
How do you use them? (Integration into QtCreator, standalone, etc.)Regards,
Markus -
wrote on 14 Dec 2010, 09:11 last edited by
Here we use pclint for static code analysis, and sometimes source monitor. But we are not using QtCreator on work, so we have integrated them in our build environment.
-
wrote on 14 Dec 2010, 11:59 last edited by
Gerolf: Nothing should stop you from integrating static code analysis into your build system even when using Qt Creator:-)
I do occassionally run "krazy":http://techbase.kde.org/Development/Tutorials/Code_Checking#The_KDE_.27Krazy.27_Checker over the code I work on. It is free, and does help to catch some Qt gotchas, even though it does not really do code analysis (it seems to be mostly regexp based).
-
wrote on 15 Dec 2010, 17:46 last edited by
You can try "cppcheck":http://sourceforge.net/apps/mediawiki/cppcheck/index.php?title=Main_Page
-
wrote on 27 Dec 2010, 21:28 last edited by
Coverity. It is commercial, but with it you can write your own code checkers.
-
wrote on 7 Sept 2011, 12:59 last edited by
You could look at using the "Clang Static Analyzer with Qt":http://qihome.org/qiliang/2011/08/08/clang-static-analyzer-with-qt/
I think there has been at least some initial work on getting Clang working with Qt Creator.