In message <[EMAIL PROTECTED]>
Marc Munro <[EMAIL PROTECTED]> wrote:
> I have a reproducible crash using libxml. I'd like some suggestions on
> how I can track this down as it's become a show-stopper for my current
> project. This is from a libxml gem created from svn this morning.
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.
When ruby then gets around to freeing the first object it crashes
trying to free the (already freed) underlying libxml object.
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.
Tom
--
Tom Hughes ([EMAIL PROTECTED])
http://www.compton.nu/
_______________________________________________
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
