Our Customers
|
PVS-Studio code analyzer is based on VivaCore Library
|
|
Sometimes the PVS-Studio code analyzer seems to find an issue in the code on which it generates a message, specifies the file name but does not show the number of the line with the issue as shown in the figure.»
Abstract When developing software products, developers need very much to get feedback from users of their programs.»
This article illustrates techniques required to employ the use of PVS-Studio static code analyzer together with continuous integration systems.»
In the article, we will compare three mechanisms of code analysis from the viewpoint of detecting 64-bit errors: the Visual C++ 2010 compiler, the Code Analysis for C/C++ component included into Visual Studio 2010 and Viva64 analyzer included into PVS-Studio 3.60.»
This article is the most complete collection of examples of 64-bit errors in the C and C++ languages.»
Terminology
Cyclomatic complexity
Cyclomatic complexity. Cyclomatic complexity of a program is a structural (or topological) measure of programs' complexity for measuring software quality. Cyclomatic complexity measuring allows you to evaluate the quality of the program code and detect high-complexity procedures. High-complexity procedures are subject to errors and detecting them is highly required to perform code review. Program cyclomatic complexity was the first topological complexity measure which was used in practice and became basis for many modifications. Measuring of cyclomatic complexity relates to static code analysis methods.
If you need to develop ad-hoc methods of calculating cyclomatic complexion or other metrics, you may try the open library VivaCore to analyze C/C++ code. Our company OOO "Program Verification Systems" can also develop ad-hoc solutions or their parts related to processing of the source code (see the section "Services. Creation of analyzers").
References
- Wikipedia. Cyclomatic complexity
- T.J. McCabe, "A complexity measure," IEEE Transactions on Software Engineering, vol. SE-2, no. 4, pp. 308-320, December, 1976.
- SourceMonitor Tool