There is a 0.5.2.1 that fixes a problem with xpath.find returns when they are empty. That is only available by an svn checkout, soon to be released as a gem. It is easy to build and after the pkg/ dir will have a gem that you can install.
Dan On Nov 16, 2007, at 17:17, uncle wrote: > I just upgraded > - feisty to gutsy > - rails 1.2.3 to rails 1.2.5 > - ruby 1.8.5 to 1.8.6 > > Turns out in the sudo gem update all, I also got gems/libxml- > ruby-0.5.2.0 > > Then I started getting random/frequent segfaults in a pretty big rails > app. The seg faults were happening in ostruct, so I went hunting all > over, downgrading, etc. Finally replaced ostruct with a 5 line home > grown class that no way had problems, and I am still seg faulting. > > Then I downgraded from 0.5.2.0 to 0.3.8.4 of libxml-ruby and poof, > things are solid as a rock again. > > I notice on the libxml-ruby site news area it stops at 0.3.8.4 (not > sure what mem2 is). > > What is the 0.5.2.0 thing, and is there anything I can provide that > can help you all get to the bottom of the segfault. I am not a gdb/ > linux guru, so getting out of my area there. > > -- Thanks > _______________________________________________ > 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
