[libxml-devel] Random crashes
Sean Chittenden
sean at chittenden.org
Fri Mar 7 16:27:38 EST 2008
> 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.
Your call for developer support is not falling on deft ears and I can
sympathize with the burden of support after a piece of software is
written. #{job} + #{real_life} + #{oss_time} ? Guess which gets
squeezed first. The economics of open source suck on the development
side of things. :-/ -sc
--
Sean Chittenden
sean at chittenden.org
http://sean.chittenden.org/
More information about the libxml-devel
mailing list