Scott wrote:
Is any of this implemented in a DLL ?
the program is haning up because its trying to register a class that is in the process of being destroyed. Try setting a break poin on the assertion on line 71 of exended_type_info.cpp and try to figure out which class is being register.
Set break point on the destructor of that class.
This might lead one to the point whereby a destructor is being called while someting is being serialized
You are correct that the class causing the problem is implemented in another DLL and imported to my server .exe. I'm not sure how to go about placing a breakpoint in the extended_type_info.cpp file. Boost was built on another computer and I only have access to the header files and lib/dlls.
My guess is that the DLL is getting unloaded "too soon". You might put a break point in the unload code of the DLL and see if that trips before the assertion. There have been problems with code explictly unloaded while the type is still "in use" in a non-obvious way. Robert Ramey