https://svn.boost.org/trac10/ticket/12549 <p> Consider two classes, Father and Child, with a circular dependency. Father contains a Child member, and Child contains a pointer to Father. </p> <p> There is a way to serialize and deserialize this structure in such a way that an extra object of type Child is created. I believe that pointer_conflict should be thrown during serialization instead. </p> <p> The created XML archive (see attachment) is consistent, so the extra object is created during deserialization. </p> <p> I observed this behavior in 1.57 and 1.62. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/12549 Trac 1.4.3 Michał Brzozowski <miki@…> Tue, 25 Oct 2016 10:47:38 GMT https://svn.boost.org/trac10/ticket/12549 https://svn.boost.org/trac10/ticket/12549 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">serial_crash.cpp</span> </li> </ul> Ticket Michał Brzozowski <miki@…> Tue, 25 Oct 2016 10:48:14 GMT https://svn.boost.org/trac10/ticket/12549 https://svn.boost.org/trac10/ticket/12549 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">filename</span> </li> </ul> <p> Serialized state </p> Ticket Robert Ramey Tue, 01 Nov 2016 21:56:59 GMT https://svn.boost.org/trac10/ticket/12549#comment:1 https://svn.boost.org/trac10/ticket/12549#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">wontfix</span> </li> </ul> <p> OK - could imagine how this might occur. But it would take me a lot of time to figure out how to fix it. I just can't spend the required time for something I'd have to regard as more than a corner case - more like a pathological case. If you want to do the work and propose a fix I'll look at it, but for now I'm going to close this with "won't fix" </p> Ticket