Boost C++ Libraries: Ticket #1037: boost.serialization : invalid pointer dependant upon serialization order

attachment set

anonymous — Wed, 06 Jun 2007 23:32:53 GMT

attachment → pointerconflict.cpp

ramey@… — Tue, 03 Jul 2007 17:00:11 GMT

User error.

Described in documentation under "archive exceptions"

Robert Ramey

owner set

Eric Niebler — Wed, 11 Jul 2007 02:02:58 GMT

owner set to Robert Ramey

status changed; resolution set

Robert Ramey — Wed, 11 Jul 2007 03:37:36 GMT

status new → closed
resolution → invalid

status changed; resolution deleted

tg38@… — Fri, 13 Jul 2007 17:22:45 GMT

status closed → reopened
resolution invalid

Replying to ramey:

Just calling for more comments if no fixes.

If this is an error, isn't it an error in both implementation, and shall raise exception in both cases?

Could you then add to documentation (in tutorial) how to save vectors of scalar type that can be pointed to by other stucture?

Still, I wonder why this is considered a "user" bug, because it seems contradictory to the library goals. When it is limitation i would be prefer early emphasis on doc.

status, severity changed; resolution set

Robert Ramey — Fri, 13 Jul 2007 19:51:12 GMT

status reopened → closed
resolution → invalid
severity Showstopper → Not Applicable

This is explained in the documentation under Reference/Special Considerations/Archive Exceptions/pointer conflict.

This occurs when an object is first loaded through a pointer, thereby creating a new object, then loading the same object to a specific place. With no exception, we would end up with two objects where we started with one before. There is no obvious way to address this without making the serialization loading multi-pass - which would create a whole host of other issues.

Note that questions like this are much better posted on the mailing list rather than filing a "bug report"

Robert Ramey