Boost C++ Libraries: Ticket #3934: serialization assertion failure on windows using DLLs

attachment set

cris@… — Tue, 16 Feb 2010 10:36:52 GMT

attachment → b.cpp

Code for DLL 1

attachment set

cris@… — Tue, 16 Feb 2010 10:37:13 GMT

attachment → d.cpp

Code for DLL 2

attachment set

cris@… — Tue, 16 Feb 2010 10:37:49 GMT

attachment → main.cpp

code for main.exe

attachment set

cris@… — Tue, 16 Feb 2010 10:38:10 GMT

attachment → b.h

Header for DLL 1

attachment set

cris@… — Tue, 16 Feb 2010 10:38:34 GMT

attachment → d.h

header for DLL 2

attachment set

cris@… — Tue, 16 Feb 2010 10:46:09 GMT

attachment → build.cmd

simple command line build for the example

cc set

crispin.boylan@… — Tue, 16 Feb 2010 10:48:54 GMT

cc crispin.boylan@… added

Robert Ramey — Fri, 26 Feb 2010 07:15:46 GMT

I've been looking into this. It looks to me that just instantiating D or C in the main module will instantiate all the code in the class which will trigger an export. At least it looks this way on windows/msvc. Could you investigate with unix by running the debugger to see if it happens with unix. There is also the question of whether it's the gcc vs msvc. I should be able to check that here as I can compile and test gcc under cygwin.

Thanks for helping out on this.

Robert Ramey

cris@… — Fri, 26 Feb 2010 09:15:07 GMT

I can certainly have a look in UNIX, although my actual program runs fine there with all versions of boost.

Interestingly (perhaps), I can make my UNIX builds fail with multiple code instantiated on 1.42 if using gcc -fvisibility=hidden and explicitly only exporting the same symbols as in my windows build. With 1.39 and the -fvisibility=hidden flag I get 'unregistered void cast' on UNIX. On 1.40 on Windows with basically the same thing (same exports handled by dllexport) I get a working program.

To use visibility=hidden to work at all I can put pragmas to enable default visibility around the boost include macros (export.hpp, text_oarchive, text_iarchive).

status changed; resolution set

Robert Ramey — Sun, 07 Mar 2010 21:02:19 GMT

status new → closed
resolution → fixed

I've looked at this and conclude that for now at least I'm just going to comment out the code which traps.

"To use visibility=hidden to work at all I can put pragmas to enable default visibility around the boost include macros (export.hpp, text_oarchive, text_iarchive)."

I would be curious to know what these pragmas are. At a minimum, this information should be added to the documentation.

Robert Ramey