您的位置:首页 > 其它

purify里面的PAR:Both Debug and non-Debug versions of CRT are active 的警告的解决办法

2006-09-08 12:00 691 查看
We are developing some application in Visual Studio. In this
application we are using some third-party libraries,
for. ex.. oci.lib (Oracle Call Interface) for which we have release
version and Rogue Wave C++ libraries (which can
be build in both debug and release versions). When I try to run the
debug build of my application under purify,
it gives me the following warning.

"PAR:Both Debug and non-Debug versions of CRT(C Run Time Library) are
active."

This warning comes because I am using the release version of oci.lib,
which will be using non-debug version of CRT, i.e.
MSVCRT.lib. While my application and Rogue Wave library is build using
DEBUG options, so it uses debug version of CRT.
This usage of both Debug and non-Debug versions of CRT may result in
heap corruption.

To remove this PAR I build the debug version of my application and
linked it with the release version of CRT and Rogue Wave
libraries. After this I no-longer get the PAR:warning, but now I will
not be able to debug the Rogue Wave Library code.

Is there any way to use the release version of the third-party
libraries such as (oci.lib) with the debug build of our
application and still not get PAR. Or what is the right way link the
debug version of our application with release version
of third-party libraries, so that we don't get PAR and are able to
debug Rogue Wave library also.

Please help us out.

Thanks
--
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: 
相关文章推荐