Tom,
Your crash is a typical one - it looks like it is caused by ruby still having a handle to a libxml object that has been attached to another libxml object that has then been freed.
Would the solution be a simple as having ruby nodes *never* freeing libxml objects except the toplevel document (since it sounds like libxml cleans up after itself).
My patches (to which I see you have already been pointed) are quite likely to help with this. They're only a band aid really though - what is really needed is a ground up review/redesign of the way the two object models are tied together as the current scheme basically doesn't work at all.
It seems like a fundamental decision has to be made - who is responsible for freeing allocated nodes. Ruby? Libxml? Having both do it, which sounds like the current situation, is obviously totally non-workable.
Charlie
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
