A double free on the context seems the likely candidate. If you can send a bug exploit that I can reproduce then there is a possibility of resolution. The stack trace is identification.
Dan On Feb 5, 2008, at 10:20, Saurabh Nanda wrote: > I have a long running RESTful web service that needs to read XML > documents from HTTP content bodies. I've noticed lots of instances > where it has randomly crashed due to an error in libxml. > > I came across the following post while digging for some clues: > http://rubyforge.org/pipermail/libxml-devel/2007-November/000586.html > > Is there a preferred (guaranteed to not crash) way of parsing XML > strings in libxml? Here's what I'm doing: > > parser=XML::Parser.new > parser.string= content > xml = parser.parse > > Is there a better way? I've attaced the error log, just in case it > helps. > > Saurabh. > -- > http://nandz.blogspot.com > http://foodieforlife.blogspot.com > <crash-log-for- > libxml.txt>_______________________________________________ > libxml-devel mailing list > libxml-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/libxml-devel _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
