https://svn.boost.org/trac10/ticket/9949 <p> In intrusive containers, the <code>safe_link</code> and <code>auto_unlink</code> hook types cause boost to reset the hooks to their default constructed state (usually <code>NULL</code>) upon removing an element from a container. That suggests a user could double check that nodes are indeed removed from all containers upon destruction, by checking that the hooks are set to <code>NULL</code>. Unfortunately, the check fails because, unlike all other regular nodes, the hooks of the container <em>header</em> nodes are not reset upon destruction of the container. </p> <p> I will create a pull request which rectifies this in <code>list</code>, <code>slist</code>, and <code>bstree</code>. I will drop it on top of the develop branch, which has the recent fix to bug <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/9940" title="#9940: Bugs: bad bug in intrusive list with safe_link (or auto_unlink) hooks (closed: fixed)">#9940</a>. </p> <p> I believe the change should have no negative impact. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/9949 Trac 1.4.3 Matei David <matei@…> Fri, 25 Apr 2014 00:21:54 GMT https://svn.boost.org/trac10/ticket/9949 https://svn.boost.org/trac10/ticket/9949 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">unlink-header.cpp</span> </li> </ul> <p> demonstrates the issue </p> Ticket Matei David <matei@…> Fri, 25 Apr 2014 00:26:33 GMT https://svn.boost.org/trac10/ticket/9949#comment:2 https://svn.boost.org/trac10/ticket/9949#comment:2 <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">fixed</span> </li> </ul> <p> Fixed in commit SHA-1: fc6d3cca5fd7e122c4b608df3e659c1120552975 </p> <ul><li>Reverted wrong commit SHA-1: 62367b52e197b1dbca5ec8ba423a2ce3bfc89790 and removed include to recently deleted "detail/clear_on_destructor_base.hpp" file. </li></ul> Ticket