Our website uses cookies to enhance your browsing experience.
Accept
to the top
close form

Fill out the form in 2 simple steps below:

Your contact information:

Step 1
Congratulations! This is your promo code!

Desired license type:

Step 2
Team license
Enterprise license
** By clicking this button you agree to our Privacy Policy statement
close form
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
* By clicking this button you agree to our Privacy Policy statement

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

close form
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

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

close form
check circle
Message submitted.

Your message has been sent. We will email you at


If you do not see the email in your inbox, please check if it is filtered to one of the following folders:

  • Promotion
  • Updates
  • Spam

Webinar: Evaluation - 05.12

>
Posts

Posts

Apr 20 2011
Comparing the VS 2010 and PVS-Studio general static analysis. Sample bugs from five open-source projects
Evgenii Ryzhkov
The article demonstrates errors detected with the static code analyzer integrated into Visual Studio 2010. The research was performed on five open source projects. The same projects were also...
...
Apr 13 2011
About our clients' practice of PVS-Studio integration
Evgenii Ryzhkov
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...
...
Subscribe to the newsletter
Want to receive a monthly digest of the most interesting articles and news? Subscribe!
* By clicking this button you agree to our Privacy Policy statement
Apr 12 2011
Why you should run static code analysis regularly and not from time to time (for instance, at "each release")
Evgenii Ryzhkov
While developing and helping people to use static code analyzers, we constantly encounter an inefficient approach to using these tools. Developers would launch the tool, find and fix...
...
Apr 08 2011
We're coming to Reddit
Andrey Karpov
Although we have plenty of materials on programming on our site www.viva64.com, programmers do not visit us often. The reason for this is that too few people know of our site and its resources.
...
Mar 31 2011
Difficulties of comparing code analyzers, or don't forget about usability
Andrey Karpov, Evgenii Ryzhkov
Users' desire to compare different code analyzers is natural and understandable. However, it's not so easy to fulfill this desire as it may seem at first sight. The point is that you don't know...
...
Mar 30 2011
An eternal question of timing
Andrey Karpov
It seemed that long forum debates about methods of measuring algorithm's running time, functions to use and precision that should be expected were over. Unfortunately, we have to return to...
...
Mar 29 2011
We've got proprietary symbols for our articles
Andrey Karpov
We publish rather many articles about software errors, code analysis and of course using our PVS-Studio static analyzer to detect issues in popular open-source projects. To make our articles...
...
Mar 29 2011
How to make fewer errors at the stage of code writing. Part N2
Andrey Karpov
This is the second article on avoiding certain errors at the early stage of code writing. In the previous post, we have already advised you to avoid a large number of calculations in one...
...
Mar 22 2011
It's difficult to make it right (of one subtle error)
Evgenii Ryzhkov
Our PVS-Studio analyzer has existed for several years. But we are still coming across "initial" errors in it, i.e. errors that have existed there for the whole life-cycle. We have checked the...
...
View more Pagination arrow previous
Showing: - of 1478