status changed

Robert Ramey — Thu, 04 May 2017 16:12:02 GMT

status new → assigned

"most of the failures look like issues with the tests" and examples as well.

Unfortunately, when making the tests and examples, I totally ignored the issue of object lifetime. Actually it should be addressed in the documentation itself since de-serialization of a pointer creates a new object which may be without an owner. It's odd that no one has complained about this. I sometimes wonder if this causes problems for some people. In any case, it prevents me from running the "sanitizers" which I would have liked to be able to do. Making alterations to support this would take a very large amount of time which is hard to justify for the serialization library these days. I'm wondering when it will be replaced.

This particular error is kind of interesting. According to the message, the complaint is in trying to downcast an object of type xml_oarchive_impl<xml_oarchive> to an object of type xml_oarchive. But I'm quite sure that xml_oarchive has xml_oarchive_impl<xml_oarchive> as a base class. So I can't really understand the message and I'm not really sure what to do about it - if anything.

Thanks for pointing this out - I'll leave this open in case I stumble upon something which sheds light on it.

Boost C++ Libraries: Ticket #12913: Undefined behaviour in serialization library

status changed