Thank you.
I've realized that after reading through some examples and tests.
Wrapping the archive instance inside its own scope fixed that.
I believe I have found the source of my problem. My program is
basically dynamically loading another module and forking a process to
run that module in. Both the parent module and the client module had
the LogMessage class exported by boost. Since the client inherited the
memory space of the parent this caused the troubles. Now I will just
figure out an elegant way to make sure that the LogMessage gets
exported only once.
Thanks for the help.
On 1/7/07, Robert Ramey
sadrok wrote:
I notice that the XML is not completed, but this doesn't seem to be a problem.
This is usually caused by closing the output stream before the archive destructor is called. Its the archive destructor which finishes up the the xml in the archive.
Robert Ramey
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
-- sadrok@gmail.com Yahoo! IM: sadrok_za Jabber ID: sadrok@jabber.obsidian.co.za