[Gnash-dev] dangers of intrusive_ptr misuse

[strk]

I just wanted to share with you a test file used to verify how dangerous is
the current use of boost::intrusive_ptr by Gnash.

Basically, the intrusive_ptr chain must NOT be broken, or premature deletion,
with consequent memory corruption will happen.

See this bug for an examplar sympthom: https://savannah.gnu.org/bugs/?18675
Note that the bug can reveal itself much later then the time in which it is
introduced, so it's worth inspecting for possible early-catcher solutions.

The attached testcase contains a "forbid-deletion" mechanism making debugging
easier. We might want to add this to gnash as well when facing similar problems
or rething the whole smart pointers model. On a side-note, it seems that 
intrusive_ptr
will be deprecated by boost dev team.

Comments welcome.

--strk;

 ()   ASCII Ribbon Campaign
 /\   Keep it simple!

intrusive.cpp
Description: Text document