Re: [Boost-users] [Serialization] Problem serializingviabaseclassptr

Hello Robert,
Sorry for not giving you feedback earlier, I was on vacation. I've included your proposed changes in my test application but I still get the same compile error:
C:/Boost/include/boost-1_33_1/boost/archive/detail/oserializer.hpp: In function `void boost::archive::save(Archive&, T&) [with Archive = boost::archive::text_oarchive, T = const A*]':
C:/Boost/include/boost-1_33_1/boost/archive/basic_text_oarchive.hpp:78: instantiated from `void boost::archive::basic_text_oarchive<Archive>::save_override(T&, int) [with T = const A*, Archive = boost::archive::text_oarchive]'
C:/Boost/include/boost-1_33_1/boost/archive/detail/interface_oarchive.hpp:78: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = const A*, Archive = boost::archive::text_oarchive]'
../main.cpp:101: instantiated from here
C:/Boost/include/boost-1_33_1/boost/archive/detail/oserializer.hpp:567: error: incomplete type `boost::STATIC_ASSERTION_FAILURE<false>' does not have member `value'
make: *** [main.o] Error 1
Could you tell me what I'm missing?
Thanks again for your help,
Guy Letourneau
Test application:
#include <iostream>
#include <fstream>
#include
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

Guy Létourneau wrote:
**** // > const A* Parent = Child; // Parent is now const // nope- Parent is not const - it points to a const A - not the same thing !!! // try const A * const Parent = Child; // const pointer to a const A // also the following will work - I believe A * const Parent = Child;

I'm running into what appears to be a bug in the serialization library, but maybe it is just a limitation on the
library's usage. I'm not getting any exceptions thrown during serialization/deserialization, but I'm getting corrupted
pointers after deserialiation.
I'm trying to serialize/deserialize an object that contains a vector of objects containing vectors (something like
below):
class TObject
{
int x;
}
class TObjectContainer
{
std::vector<TObject> ObjectVector;
};
class TRoot
{
std::vector<TObjectContainer> ObjectContainerVector;
std::vector

Ivan wrote:
This certainly looks like a bug to me - good call
TObjects are de-serialized to the heap then added to the vector. Since the tracking saves the address TObject is serialized to, the address would be on the stack. reset_object_address sets the tracked address to the heap address after the item is appended to the vector. I thought I considered the case of a vector of vectors - but maybe not. I would expect that the objects get theire addresses fixed up twice- once when they are moved from the stack to the heap and once when the vector container itself is moved from the stack to the heap. Its possible that there is something missng . Robert Ramey
best regards,
Dan Notestein

Robert Ramey wrote:
Yes, the TObjects are fixed up twice, but I think the second fixup is an error because vector<> doesn't really contain the data elements, it contains a ptr to the data elements. When the vector container is "copied" from the stack to the heap, the newly allocated internal vector element array will be randomly allocated from somewhere else in the heap, so using an offset based off the address of the new copy of the vector container won't work. I can think of two possible theoretical solutions to the problem: 1) Use the container::swap function to exchange internal data ptrs of the stack and heap copy of the vector. This gives the heap vector the ownership of the stack vector's elements. This seems the most efficient technique since it avoid reallocating and copy constructing the elements. There's also no need to fixup the ptrs to the elements using this technique. 2) Continue to use the copy constructor for the vector when transferring the vector from stack to heap, and use the internal array ptr inside the new copy of the vector to fixup the elements. This definitely seems like the lesser of the two options. I would have tried to make a fix for this, but the algorithm for handling the moveable ptrs that define the range of addresses to fixup was a little complicated for me to follow. In particular, I wasn't sure how to make the fixups take place so that truly "contained" data gets fixed up, while avoiding fixing up the data that is merely "pointed" to by data members (and hence shouldn't be fixed up when the container is copied). One idea I had was to keep around the size of the data objects being moved, so that the reset_address function could look for ptrs in the moveable_ptr range that have addresses between old_address and old_address+object_size. But I also figured there was a good chance that there is already information available somewhere on which items in the object_id table are "contained" vs "pointed to". best regards, Dan Notestein
participants (4)
-
Dan Notestein
-
Guy Létourneau
-
Ivan
-
Robert Ramey