PVS-Studio Static Code Analyzer for 64-bit and parallel C/C++ code
Our Customers
|
PVS-Studio code analyzer is based on VivaCore Library
|
|
02.09.2010
Feeling the new Intel Parallel Studio XE 2011 beta
So I've gotten to try the C++ compiler included into Intel Parallel Studio XE 2011 beta at last.»
So I've gotten to try the C++ compiler included into Intel Parallel Studio XE 2011 beta at last.»
30.08.2010
Five days for fixing a two-character error, or a myth of almighty technologies aiding software development
In this blog, you may often read posts about how this or that software tool or software development technology helps make fewer errors, find them faster and correct them easier.»
In this blog, you may often read posts about how this or that software tool or software development technology helps make fewer errors, find them faster and correct them easier.»
30.08.2010
d'Artagnan and Internet, or working on the problem of bad links
Friends, it is high time we stopped considering links only in the context of their number and buying/ selling and counting PR of the site they are laid out on.»
Friends, it is high time we stopped considering links only in the context of their number and buying/ selling and counting PR of the site they are laid out on.»
22.07.2010
Using PVS-Studio with continuous integration systems
This article illustrates techniques required to employ the use of PVS-Studio static code analyzer together with continuous integration systems.»
This article illustrates techniques required to employ the use of PVS-Studio static code analyzer together with continuous integration systems.»
06.07.2010
Comparing capabilities of PVS-Studio and Visual Studio 2010 in detecting defects in 64-bit programs
In the article, we will compare three mechanisms of code analysis from the viewpoint of detecting 64-bit errors: the Visual C++ 2010 compiler, the Code Analysis for C/C++ component included into Visual Studio 2010 and Viva64 analyzer included into PVS-Studio 3.60.»
In the article, we will compare three mechanisms of code analysis from the viewpoint of detecting 64-bit errors: the Visual C++ 2010 compiler, the Code Analysis for C/C++ component included into Visual Studio 2010 and Viva64 analyzer included into PVS-Studio 3.60.»
29.06.2010
A Collection of Examples of 64-bit Errors in Real Programs
This article is the most complete collection of examples of 64-bit errors in the C and C++ languages.»
This article is the most complete collection of examples of 64-bit errors in the C and C++ languages.»
Knowledge Base
Confusion of WPARAM with UINT, and LPARAM with LONG
A great deal of compilation errors occurring when trying to recompile a 32-bit Windows application for 64-bit systems is related to inccorect function arguments. You may often see that in user code UINT and LONG types are used instead of WPARAM and LPARAM as function arguments. Here is an example:
//Function definition in the class virtual LRESULT OnTrayNotification(WPARAM uID, LPARAM lEvent); //Function implementation LRESULT CSystemTray::OnTrayNotification(UINT wParam, LONG lParam)
In Win32 the type WPARAM coincides with UINT and LPARAM coincides with LONG. In Win64 these are different types, so you must correct the code. See also the post "A common error occurring when compiling a 64-bit application: error C2440, OnTimer" on this topic.