Passing STL references across DLL boundaries in VS.Net 2003 (VC++ 7.1)

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ross Burns - 18 Feb 2004 04:31 GMT

I am thinking about moving my app to VC++ 7.1 - I wanted to know if
the annoying problem of access violations when passing STL-related
structures across DLL-EXE boundaries and accessing them has been
resolved (assume both link to the same CRT). Thanks!

Reply to this Message

Doug Harrison [MVP] - 18 Feb 2004 05:10 GMT

>I am thinking about moving my app to VC++ 7.1 - I wanted to know if
>the annoying problem of access violations when passing STL-related
>structures across DLL-EXE boundaries and accessing them has been
>resolved (assume both link to the same CRT). Thanks!

Assuming you mean "same CRT DLL" when you say "same CRT", I believe the
answer to your question is "yes". You'll never be able to do this linking
statically.

Also, which version are you using now that has the problem, and which
classes are you talking about? There are some fixes posted here for VC5/VC6,
and "Fix to <xtree>" solves the problem for the associative containers:

http://www.dinkumware.com/vc_fixes.html

Signature

Doug Harrison
Microsoft MVP - Visual C++

Reply to this Message

tom_usenet - 19 Feb 2004 12:08 GMT

>>I am thinking about moving my app to VC++ 7.1 - I wanted to know if
>>the annoying problem of access violations when passing STL-related
[quoted text clipped - 4 lines]
>answer to your question is "yes". You'll never be able to do this linking
>statically.

Unless you use a custom allocator (that uses OS memory
allocation/deallocation functions), which is a pain without template
typedefs.

Tom

C++ FAQ: http://www.parashift.com/c++-faq-lite/
C FAQ: http://www.eskimo.com/~scs/C-faq/top.html

Reply to this Message

Doug Harrison [MVP] - 19 Feb 2004 18:49 GMT

>>>I am thinking about moving my app to VC++ 7.1 - I wanted to know if
>>>the annoying problem of access violations when passing STL-related
[quoted text clipped - 8 lines]
>allocation/deallocation functions), which is a pain without template
>typedefs.

Chances are, someone who wants to share STL objects across module boundaries
will share other CRT state, so the only solution I'd consider would be
linking to the same CRT DLL. In addition, the allocator solution might work
for vector<int,A>, but it might not help vector<T,A> where T does memory and
other resource allocation internally.

Signature

Doug Harrison
Microsoft MVP - Visual C++

Reply to this Message

Rate this thread:

Passing STL references across DLL boundaries in VS.Net 2003 (VC++ 7.1)

Free Magazines