To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (extended version)
* By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
About our clients' practice of PVS-Stud…

About our clients' practice of PVS-Studio integration

Apr 13 2011

Sometimes our potential clients ask about examples of successful integration of PVS-Studio in various companies. Their interest is understandable. After Case Study by Microsoft in the form "the Formual-1 McLaren team has begun to use the new SQL Server and their results has become so much better that..." you really want to see benefit from a particular tool.

But for small companies (us being such a company) it is difficult to make such materials due to organizational and juridical issues.

First, the point is in the way a product is being sold. We are selling our solution through the Internet and it is not always the end user who makes the purchase. For instance, some large company (like Intel) buys a license through some reseller (for instance, SHI). All that happens without our people participating. And although we see that some company has bought the product for some client, the client's contact information is most likely information of the procurement department. So, sometimes we cannot even communicate with the end user.

Second, the juridical aspect often does not permit the client company's employee to disclose such information as, for example, organization of the development infrastructure: how many and what build systems are used, what management systems are used, how many developers participate in the process and so on. While Microsoft can push coordination of all these data through the McLaren management, small organization hardly can do that.

Because of this, it is almost impossible to give information about instances of successful integration and especially errors found with the help of the analyzer.

But we see another way to show that we are actively participating in integrating PVS-Studio into the development process and do not leave our clients alone with our tool. We can tell you about modifications we do for them by their requests.

First of all, we always improve the analyzer if it does not process some code fragments completely. Incomplete support of the language might seem a drawback of the analyzer - but no analyzer can actually boast about support for all the types of templates or C++0x syntax; even compilers might have errors. We always quickly and efficiently solve issues related to incomplete parse of code.

Some clients might need diagnostic of specific errors. Sometimes they offer new diagnostic rules themselves, sometimes they only show us errors and we formulate the rules. Anyway, implementation of diagnostic rules for a particular client is a very important part of our support.

Convenient integration of code analyzers into the development process is a guarantee of its satisfactory use. We have implemented the following features by requests of our clients:

  • launch of the tool from the command line for automatic call from continuous integration systems;
  • selective check of project/solution files (by names or modification time - for instance, for the last day);
  • mask elimination of files and folders from analysis;
  • filters of diagnostic messages (by error code, by message text);
  • many other things.

In conclusion we should say that we always and quickly help users to solve any issues since we are a small company for now :-).

Popular related articles
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…

Comments (0)

Next comments
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →
Accept