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

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.

>
>
A brief note about MISRA

A brief note about MISRA

Oct 06 2016
Author:

We are often asked whether the PVS-Studio analyzer supports MISRA standard. I decided to write a short note to make it easy to answer the letters, giving the link. A brief answer - we do not currently support standards MISRA C, MISRA C++ and do not plan to do that. Here is a detailed explanation of our position concerning this question.

In connection with starting PVS-Studio support of different compilers for embedded platforms we've changed our position regarding MISRA. Starting with the version PVS-Studio 6.27, the analyzer supports MISRA C and MISRA C++ standards. Read more.

We have never focused on the support of the MISRA C, MISRA C++ and other related standards. We are aimed at searching real bugs, not the prevention of potential problems by limiting programmers.

For example, we don't induce the programmers to write break in swicth, and don't prohibit using goto. We think there is little use in the recommendation of using // comment instead of /* */. We also don't see the point to warn C programmers that they have address arithmetic p++ in their program.

Such diagnostics bulk up the analyzer output and instead of searching for real errors, a person starts fighting with thousands theoretically good, but having no influence suggestions of the code improvement.

We have chosen a different path. None of the standards says, "avoid typos". Still, everybody makes typos. Our analyzer is very helpful in this regard. For example V501 diagnostic itself is a great way to protect against them. Such diagnostics are our competitive advantage.

Yes, we can partly take something from MISRA. This means that some things are definitely useful and at the same time appear in different standards and analyzers.

At this time we do not plan to support MISRA. We understand that some programmers may need to support this standard. But we don't want to clutter up the analyzer. And I think that's OK. If there is a need for the code to comply with the MISRA standard, there are plenty of tools that allow doing that.

Analyzers that check the compliance of the code with the MISRA standard:

  • Coverity by Synopsys
  • Klocwork by Rogue Wave Software
  • LDRA Testbed by Liverpool Data Research Associates
  • Parasoft C/C++test by Parasoft
  • PC-Lint by Gimpel Software
  • Polyspace by MathWorks
  • QA-C by Programming Research
  • Understand by SciTools
  • and so on

As you see, there are many tools, able to give recommendations about writing more qualitative code.

If you want to search for real errors, then that's our task!

Demonstration of PVS-Studio abilities in the detection of REAL bugs in the code:

  • Errors found in Open Source projects (at the time of writing this article, we have already more than 10500 errors).
  • Articles about the check of well-known open source projects with the help of PVS-Studio.
Popular related articles
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…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
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 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…
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…
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…
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…
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…
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…

Comments (0)

Next comments

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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