Примеры использования The static analysis на Английском языке и их переводы на Русский язык
{-}
-
Official
-
Colloquial
The static analysis technique is the most appropriate method to detect 64-bit errors.
However, this article is about bugs,not the static analysis methodology.
The static analysis approach has many supporters and are many interesting articles on this approach.
Here you may see other samples of this error found through the static analysis method.
Люди также переводят
This switch allows you to launch the static analysis module integrated into Team System to search for some errors in code.
Here is what we can say to those who aren't new to the static analysis tools.
Perhaps, if the project authors used the static analysis regularly, the overall picture would be more positive.
While catching and fixing bugs in new code,you will quickly get to value the might and usefulness of the static analysis methodology.
This mode allows increasing the speed of the static analysis on the continuous integration server.
While communicating with people on forums,I noticed there are a few lasting misconceptions concerning the static analysis methodology.
However, the ratio benefits/price makes the static analysis quite a useful method, adopted by many companies.
Before we continue with our tool's development history,I would like to talk about the static analysis technology as such.
All in all, our main goal is to popularize the static analysis methodology in general, and the PVS-Studio analyzer in particular.
This paper describes the static analysis tool for finding program entities, their metrics, and relations between entities.
May you find as many errors as possible using the static analysis methodology I love so much!
In this paper we review the static analysis tool developed in ISP RAS for finding critical errors and security vulnerabilities in C/C++ source code.
I will be describing an ideal process of integrating the static analysis methodology into one's software project.
Detection of porting errors should be started at the stage of code editing/recompilation already- it is possible if you use the static analysis methodology, for example.
In the article"Copy-Paste andmuons" I was reasoning about how useful the static analysis methodology is and about the PVS-Studio analyzer's diagnostic abilities.
With the emergenceof PVS-Studio for Linux, the ability of adding the static analysis to other methods of testing a project on this platform, including the Docker, became available for users.
PVS-Studio static analyzer is installed on the machines of the developers, who do the incremental analysis after the local build of the solution, and on the continuous integration server,where the static analysis is performed for the whole code during the night build.
It is SUGGESTED that at least one of the static analysis tools used for the static_analysis criterion include rules or approaches to look for common vulnerabilities in the analyzed language or environment.
Other samples of errors and vulnerabilities detected with the help of the static analysis methodology can be found here.
In this case, performing the static analysis of the whole code will significantly increase the build time, which will make the use of static analysis during numerous daily builds almost impossible.
In the next lesson you will learn in more detail about the static analysis methodology and PVS-Studio tool.