在一个过程中混合和匹配Visual C ++运行时DLL文件有多糟糕？ [英] How bad is it to mix and match Visual C++ runtime DLL files in one process?

问题描述

我有一个使用Visual Studio 2012构建的应用程序，因此它取决于 MSVCP110.DLL 和 MSVCR110.DLL 。我正在使用另一个DLL文件，该文件似乎是使用Visual Studio 2010构建的，并且依赖于 MSVCP100.DLL 和 MSVCR100.DLL 。我使用的另一个DLL是使用Visual Studio 2008构建的，并且依赖于 MSVCR90.DLL 。

I have an application that is built with Visual Studio 2012, and thus it depends on MSVCP110.DLL and MSVCR110.DLL. I'm using another DLL file, which seems to have been built with Visual Studio 2010 and depends on MSVCP100.DLL and MSVCR100.DLL. Yet another DLL I have was build with Visual Studio 2008 and depends on MSVCR90.DLL.

这是吗？一件坏事？真的很糟糕吗？我应该担心吗？我问的原因是运行时堆分配器抱怨堆损坏。这可能与混合的运行时版本有关吗？

Is this a bad thing? A really bad thing? Should I be worried? The reason I ask is that the runtime heap allocator is complaining about heap corruption. Could this be related to the mixed runtime versions?

推荐答案

主要是混合和匹配来自不同编译器版本的Visual Studio运行时并不安全因为每个运行时都会创建自己的独立堆。由于堆将是完全独立的，因此您不能使用1个堆分配内存并将其释放到另一个堆中。这样做会破坏您的堆。损坏通常不会立即导致崩溃，因为在接下来的几次分配或释放中可能无法访问堆的损坏部分，因此很难调试。

It's not safe to mix and match Visual Studio runtimes from different compiler versions mainly because each runtime will create its own independent heap. Since the heaps will be totally independent you can not allocate memory using 1 heap and free it in a different heap. Doing so will corrupt your heaps. The corruption does not usually cause an immediate crash since the corrupt part of the heap may not be accessed on the next few allocations or deallocations so it can be very hard to debug.

对于单个dll具有与应用程序不同的堆的情况，可以以非常有限的方式解决该问题。您必须隔离dll，以便dll的所有分配和释放都仅在dll内部发生。而且隔离也必须走另一条路。没有隔离，dll将无法安全地从applicaton中释放内存。

For the case of a single dll having a different heap than the application it is possible to work around the problem in a very limited way. You would have to isolate the dll such that all allocations and deallocations of dll happens only inside of the dll. And also isolation would have to go the other way as well. The dll will not be able to safely free memory from the applicaton without isolation.

有关混合CRT版本导致的堆损坏的更多信息，请参见：
http://siomsystems.com/mixing-visual-studio-versions/

More info on heap corruption caused by mixing CRT versions can be found here: http://siomsystems.com/mixing-visual-studio-versions/

编辑（2020年4月1日）：
以上答案早于Visual Studio2015。VisualStudio 2015到2019之间是二进制兼容的，但不兼容

Edit (April 1, 2020): The answer above predates Visual Studio 2015. Visual Studio 2015 through 2019 are binary compatible with each other but not compatible with any previous version.

以下链接讨论了这些版本之间的二进制兼容性： https://docs.microsoft.com/zh-cn/cpp/porting/binary-compat-2015-2017?view = vs-2019

The following link discusses the binary compatibility between these versions: https://docs.microsoft.com/en-us/cpp/porting/binary-compat-2015-2017?view=vs-2019

这篇关于在一个过程中混合和匹配Visual C ++运行时DLL文件有多糟糕？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！