Can debug/release versions of dynamic library *.dll files be mixed (cross used)?

1、 The phenomenon ：

Use some third-party dll, such as opencv, Will be generated separately debug and release Of dll, stay exe Must reference the specified version of dll, Can't mix , Otherwise it will go wrong ;

But there are also some third-party dll, such as halcon, Only for users release Of dll, User debug Version and release Version of exe You can quote this dll.

So it seems , There are some dll It can be mixed up （ Cross reference ）, Some can't , Why are there differences between the two ？

2、 reason

such as debug Of exe call release Compile generated dll, If the parameters of the interface function are used std::vector perhaps std::string Things like that , It's bound to collapse . because stl stay release and debug Different implementation under .std::string stay debug and release The memory size in the environment is inconsistent . If you mix , Memory collapse will occur .

3、 Conclusion

Not included stl Library debug Dynamic library and release The dynamic library is in debug or release You can use ;

contain stl Of debug Dynamic library and release Dynamic libraries cannot be mixed in projects ,debug Project must use debug library , release Project must use release library ;

Who allocates memory will release it , Do not use the dynamic library export function stl, Use only basic types or interfaces ;

4、 reference

dll stay debug and release How to cross reference in mode ？ - You know

Packaging Library ： c/c++ debug Version Library and release Version Library Interoperability issues _XHW___001 The blog of -CSDN Blog