I ran into this as well installing the 0.5.3 gem on both CentOS and
Fedora platforms. To get it working I had to rebuild the .so file
manually after the gem install:
cd /usr/local/lib/ruby/gems/1.8/gems/libxml-ruby-0.5.3
ruby xml/libxml/extconf.rb
make
make install
make distclean
The make inst
Dan,
I am only working with libxml through the TAP class. It is a single XML
document being parsed with a moderate number of accesses to that
document. All of the SEGV do have the garbage_collect line at
approximately the same spot.
I started putting what I am doing together as a test case t
Dan,
This one occurs even less frequently than the last one, but
unfortunately it still segfaults occasionally when garbage collection
kicks in. It appears to crop up in random places (inside active-record,
inside erb, etc.) instead of just when the XML document access is
occurring like the p
Dan,
The TAP code I pasted in the original email is fine to use for a test
case. As far as the XML document, let me create a smaller version of
the one you currently have with the stuff I don't need ripped out of it
and send that to you in place of the current XML document you have so
the res
I'm using the XML::Parser to parse XML data passed in as a string. The
parse works fine and my code then goes on to access elements and
attributes in the resulting document. If I use this code outside of the
Ruby on Rails environment, I never have any segfaults and everything
works as expecte
