# Libxml-ruby segfault on CentOS 5 (64 bit)

**URL:** <https://www.ruby-forum.com/t/libxml-ruby-segfault-on-centos-5-64-bit/153871>\
**Category:** Ruby\
**Created:** [November 22, 2008, 2:13am UTC](https://www.ruby-forum.com/t/libxml-ruby-segfault-on-centos-5-64-bit/153871 "2008-11-22T02:13:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hoshbad](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/e274bd/32.png) [@hoshbad](https://www.ruby-forum.com/u/hoshbad)\
**Post date:** [November 22, 2008, 2:13am UTC](https://www.ruby-forum.com/t/libxml-ruby-segfault-on-centos-5-64-bit/153871/1 "2008-11-22T02:13:32Z")

</div>

Hello all,  
Wondering if anyone has had issues with libxml-ruby segfaulting on  
64-bit CentOS 5. This problem is reproducible both using the yum  
installed version of Ruby (1.8.5) and Ruby 1.8.7-p72 (compiled from  
source). I’m at my wits end here – the problem seems to be reproducible  
only on 64 bit linux.

-bash-3.1$ ruby -v  
ruby 1.8.5 (2006-08-25) [x86\_64-linux]  
-bash-3.1$ uname -a  
Linux myhost 2.6.18-8.el5 #1 SMP Thu Mar 15 19:46:53 EDT 2007 x86\_64  
x86\_64 x86\_64 GNU/Linux  
-bash-3.1$ rake all  
(in /path/to/my/rake/file)  
my\_script\_which\_uses\_libxml\_ruby.rb:65: [BUG] Segmentation fault  
ruby 1.8.5 (2006-08-25) [x86\_64-linux]

I’m not really sure where to begin in asking for help – I’ve never had  
this kind of issue before. The offending method looks as follows:

def set\_cdata\_client\_mapping\_by\_name(name, cdata)  
node = get\_vcs\_root\_by\_name(name)  
client\_mapping = node.first.find(“param[@name=‘client-mapping’]”)  
client\_mapping.first.first.remove! #Segfault here - this is line 65  
client\_mapping.first.child\_add XML::Node.new\_cdata(cdata)  
end

Anyone have any insight? I would be very grateful.

---

<div class="post-metadata">

**Author:** ![hoshbad](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/e274bd/32.png) [@hoshbad](https://www.ruby-forum.com/u/hoshbad)\
**Post date:** [November 22, 2008, 2:25pm UTC](https://www.ruby-forum.com/t/libxml-ruby-segfault-on-centos-5-64-bit/153871/2 "2008-11-22T14:25:05Z")

</div>

hi sebastian!

Zitat von “Sebastian W.” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):

> Wondering if anyone has had issues with libxml-ruby segfaulting on  
> 64-bit CentOS 5. This problem is reproducible both using the yum  
> installed version of Ruby (1.8.5) and Ruby 1.8.7-p72 (compiled from  
> source). I’m at my wits end here – the problem seems to be reproducible  
> only on 64 bit linux.  
> you might want to have a look at the 0.9.3 release charlie just put out  
> (see  
> [1]). haven’t tried it myself yet as i’m not at home right now, but i  
> suppose  
> it should fix the issue.

[1]  
[http://rubyforge.org/tracker/index.php?func=detail&aid=22909&group\_id=494&atid=1971](http://rubyforge.org/tracker/index.php?func=detail&aid=22909&group_id=494&atid=1971)

cheers  
jens

---

<div class="post-metadata">

**Author:** ![hoshbad](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/e274bd/32.png) [@hoshbad](https://www.ruby-forum.com/u/hoshbad)\
**Post date:** [November 25, 2008, 1:03am UTC](https://www.ruby-forum.com/t/libxml-ruby-segfault-on-centos-5-64-bit/153871/3 "2008-11-25T01:03:31Z")

</div>

> you might want to have a look at the 0.9.3 release charlie just put out

Yes, yes, oh yay! OMG…so happy. This appears to have fixed the issue.  
I re-ran my tests after updating to 0.9.4 (fast team - a new release  
between Friday and today!) and now they’re all green.

Thanks so much jens!

---

<div class="post-metadata">

**Author:** ![hoshbad](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/e274bd/32.png) [@hoshbad](https://www.ruby-forum.com/u/hoshbad)\
**Post date:** [November 25, 2008, 10:23am UTC](https://www.ruby-forum.com/t/libxml-ruby-segfault-on-centos-5-64-bit/153871/4 "2008-11-25T10:23:58Z")

</div>

Sebastian W. [2008-11-25 00:58]:

> Yes, yes, oh yay! OMG…so happy. This appears to have fixed the  
> issue. I re-ran my tests after updating to 0.9.4 (fast team - a  
> new release between Friday and today!) and now they’re all green.  
> yeah, me too 🙂

> Thanks so much jens!  
> thank you, but it’s charlie who deserves all the gratitude!

cheers  
jens