Why does this program crash: passing of std::string between DLLs

by

This isn’t actually being caused by differing heap implementations – the MSVC std::string implementation doesn’t use dynamically allocated memory for strings that small (it uses the small string optimization). The CRTs do need to match, but that isn’t what bit you this time.

What’s happening is that you’re invoking undefined behaviour by violating the One Definition Rule.

The release and debug builds will have different preprocessor flags set, and you’ll find that std::string has a different definition in each case. Ask your compiler what sizeof(std::string) is – MSVC10 tells me that it’s 32 in a debug build and 28 in a release build (this isn’t padding – 28 and 32 are both 4 bytes` boundaries).

So what’s happening? Variable s is initialized using the debug version of the copy constructor to copy a release version of std::string. The offsets of the member variables are different between the versions, so you copy garbage. The MSVC implementation effectively stores begin and end pointers – you’ve copied garbage into them; because they’re no longer null, the destructor tries to free them and you get an access violation.

Even if the heap implementations were the same it would crash, as you’re freeing garbage pointers to memory that was never allocated in the first place.

In summary: the CRT versions need to match but so do the definitions – including the definitions in the standard library.

More Related Contents:

  1. Will new return NULL in any case?
  2. Getting LibCurl to work with Visual Studio 2013
  3. Can I pass std::string to a DLL?
  4. what does __declspec(dllimport) really mean?
  5. How to export a C++ class from a dll? [duplicate]
  6. DLL References in Visual C++
  7. Memory allocation and deallocation across dll boundaries
  8. C++ delete does not free all memory (Windows)
  9. Why can’t Visual Studio find my DLL? [duplicate]
  10. How do malloc() and free() work?
  11. How to determine if a string is a number with C++?
  12. Macro for dllexport/dllimport switch
  13. Compelling examples of custom C++ allocators?
  14. How to get available memory C++/g++?
  15. How does a C++ reference look, memory-wise?
  16. Any reason to overload global new and delete?
  17. Are memory leaks “undefined behavior” class problem in C++?
  18. C++ Compiler Error C2280 “attempting to reference a deleted function” in Visual Studio 2013 and 2015
  19. Why floating point value such as 3.14 are considered as double by default in MSVC?
  20. Check if a pointer points to allocated memory on the heap
  21. Reason why not to have a DELETE macro for C++
  22. How to play or open *.mp3 or *.wav sound file in c++ program? [closed]
  23. Why, really, deleting an incomplete type is undefined behaviour?
  24. Layout of compiled objects
  25. trying to use VideoCapture and imshow(), raises Assertion failed (size.width>0 && size.height>0) in cv::imshow
  26. Finding “dead code” in a large C++ legacy application [closed]
  27. How to load a custom binary resource in a VC++ static library as part of a dll?
  28. Memory-efficient C++ strings (interning, ropes, copy-on-write, etc) [closed]
  29. Win32: Bring a window to top
  30. reading an application’s manifest file?

Leave a Comment