|
|
|||
![]() PVS-Studio Static Code Analyzer for 64-bit and parallel C/C++ code
|
|||
![]() ![]() ![]() ![]() ![]()
28.06.2010
Why is the number of the line where an issue was found sometimes absent in the Error List in PVS-Studio? 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.»
07.06.2010
Communication between developers and users Abstract When developing software products, developers need very much to get feedback from users of their programs.» ![]()
22.07.2010
Using PVS-Studio with continuous integration systems This article illustrates techniques required to employ the use of PVS-Studio static code analyzer together with continuous integration systems.»
06.07.2010
Comparing capabilities of PVS-Studio and Visual Studio 2010 in detecting defects in 64-bit programs 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.»
29.06.2010
A Collection of Examples of 64-bit Errors in Real Programs
This article is the most complete collection of examples of 64-bit errors in the C and C++ languages.» ![]()
22.07.2010
We released a new version of PVS-Studio code analyzer - PVS-Studio 3.61»
10.06.2010
We released a new version of PVS-Studio code analyzer - PVS-Studio 3.60. »
19.05.2010
Our workers visited the GDC2010 conference that was held on May, 14-16, 2010, in Moscow and talked to many developers who participated there.»
|
Code Analyzers![]() The author of the article focuses on improving the process of C++ code development. He describes the main things to be considered while analyzing, debugging and enhancing the code. These include using static analysis tools, creating a suite of unit and regression tests and so on. The article is divided into four sections devoted to various techniques and contains code samples.
Integrating static analysis into software development provides the programmer with many advantages. The article reviews the most popular static analysis tools in several classifications including tools for Java analysis, security tools, etc. The authors also focus on various aspects of integrating static analysis such as creation of a coding standard, implementation of automated checking, the process of code review, results retention, managing new and existing code, and training engineers.
Stack overflows might be very dangerous in high-integrity systems and are difficult to detect and debug, so it is very important to prevent them by analyzing the stack beforehand. This article explains how static stack analysis can help accomplish this task and what obstacles can threaten it and also gives some tips on how to use the compiler and special AdaCoreÒs GNATstack tool for stack analysis.
The author of this note provides a list of tools for C++ analysis where he describes various commercial and open-source tools. For each item there are a brief description and a link to the related site.
This blog-post concerns the technique of searching bugs in source-code lines of various projects with the help of the new tool Google Code Search. The author explains how one can easily use this tool to detect flaws in code by typing particular expressions and characters in the search line. There are some examples provided that illustrate this technique very clear.
This article will be interesting for every user involved in C++ programming while it describes the authors' effort to investigate the most popular C++ code analyzers on the basis of special rules and sample error patterns to be analyzed by the tools. The description of the testing base and the results are thoroughly commented and shown in various tables and code samples.
Nowadays, when medicine employs complex devices for treating patients, software used in them must be secured from any defects and bugs. The paper concerns static analysis of such software systems. There are several sections that describe the essence of static analysis method, defect classes both common for software development on the whole and specific for medical devices, the task of choosing the best static code analysis tool and factors to consider while making this choice.
Wiki-resource devoted to static code analysis. It describes the essence of this technology and provides a lot of links to other materials on static analysis tools and related domains.
The paper is devoted to Parasoft Corporation's technology BugDetective for flow analysis that provides developers with many benefits such as the possibility of quick modification of code, flexible testing system, focusing on actual defects and errors, etc. The paper describes very thoroughly the working principle of BugDetective and how it can be used in combination with other testing techniques and includes many illustrative code samples and screenshots.
Pages: 1 2
|
||
|
© 2008 - 2010, OOO "Program Verification Systems"
300027, Russia, Tula, P.O. Box 1800. Office: Russia, Tula, Kutuzova 100-73 |
|||