On Fri, 2008-03-07 at 13:27 -0800, Sean Chittenden wrote:
> > I have contemplated abandoning support, but I would rather not. Being
> > the only coder makes it harder as ultimately every bug is my problem.
> > But that is not the issue, ruby 1.8 is. I have considered moving to
> > rubinius to see if their compatibilty api is better than the original.
> > But that may yield nothing as it could work fine there. 1.9 I have not
> > considered, but valgrind is sort of a white elephant since the GC
> > screws things up without a trace before the real problem occurs.
>
> Hey Dan. Check out this post:
>
> http://sean.chittenden.org/news/2008/01/12/
>
> I think that trick may be infinitely more useful in debugging the kind
> of class of problem you're describing.
A little known feature of glibc is mtrace which does pretty much the
same thing. See man mtrace / info mtrace for details.
Jon
_______________________________________________
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
