Memory allocation and deallocation across dll boundaries

Question

I understand that memory allocations made in one dll then subsequently free\'d in another can cause all sort of problems, especially regarding the CRT. These sorts of probl

Answer 1

You might try looking to see if there are any formal C++ rules for what happens when an exception is thrown in one DLL and caught in another and then goes out of scope -- it seems very similar. For exceptions, I think you are required to provide a copy constructor with a special signature, though I'm unsure now exactly what it is.