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 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.

>
>
OOO "Program Verification Systems&…

OOO "Program Verification Systems" announces the issue of a new version of the static code analyzer - VivaMP 1.10

Apr 20 2009
Author:

OOO "Program Verification Systems" announces the issue of a new version of the static code analyzer - VivaMP 1.10. VivaMP tool is designed for searching parallel errors in the code of applications developed in C++ language with the use of OpenMP technology.

In the new version, class static functions support is enhanced, this lets perform more precise diagnostics.

The mechanism which hides double errors in header files indicated in relative views has been enhanced. Before that, during a project testing, the error in #include "lib\file.h" and #include "lib\..\lib\file.h" would be considered as if located in different files. Two diagnostic warnings would be given. Now paths are exposed, and the analyzer does not indicate twice the errors contained in the file "file.h".

Three new diagnostic rules connected with the use of exceptions inside parallel regions have been added. According to OpenMP specification, exceptions generated inside a parallel region are to be caught and processed inside this region with the use of try/catch constructions. The analyzer diagnoses the following situations:

V1301. The 'throw' keyword cannot be used outside of a try..catch block in a parallel section

V1302. The 'new' operator cannot be used outside of a try..catch block in a parallel section.

V1303. The FOO function which throws an exception cannot be used in a parallel section outside of a try..catch block.

Popular related articles


Comments (0)

Next comments next comments
close comment form