Marc,
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.
Can you provide the test data? That would be hugely helpful. Also what OS, platform, etc?
I can write and debug C but I'd like some suggestions on what to look for, and what to try. I am inclined to modify all calls to free() to zero or set the allocated memory chunk before freeing it in the hope that this will make it obvious where things are breaking.
Having not hacked ruby before I am not sure how easy this will be. I'm also wondering whether any of the standard C memory testing tools can be easily incorporated into the ruby build.
I've successfully used Valgrind.
I'd welcome any suggestions/random thoughts/shared experiences/anything from anyone at this stage :-)
Did you try these patches? http://rubyforge.org/pipermail/libxml-devel/2007-June/000314.html Charlie
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
