# Seg faults with 1.8.6

**URL:** <https://www.ruby-forum.com/t/seg-faults-with-1-8-6/120222>\
**Category:** Ruby\
**Created:** [November 14, 2007, 9:47pm UTC](https://www.ruby-forum.com/t/seg-faults-with-1-8-6/120222 "2007-11-14T21:47:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [November 14, 2007, 9:47pm UTC](https://www.ruby-forum.com/t/seg-faults-with-1-8-6/120222/1 "2007-11-14T21:47:38Z")

</div>

I recently upgraded from ruby 1.8.5 to 1.8.6. At first I was using  
the prebuilt binaries that come with Ubuntu Gutsy, but now I am using  
a built from source version of 1.8.6 p110.

I am seeing seg faults several times a day in my rails applications  
(was hoping moving to the latest release would fix it).

Here is the latest…

/usr/lib/ruby/1.8/ostruct.rb:74: [BUG] Segmentation fault  
ruby 1.8.6 (2007-09-23) [i686-linux]

Aborted

$ ruby --version  
ruby 1.8.6 (2007-09-23 patchlevel 110) [i686-linux]

This is a big problem for us, any ideas on how to solve it. Note the  
seg fault does not always happen in ostruct, although it has happened  
there numerous times.

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [November 14, 2007, 9:48pm UTC](https://www.ruby-forum.com/t/seg-faults-with-1-8-6/120222/2 "2007-11-14T21:48:48Z")

</div>

On Nov 14, 2:41 pm, “removed\_email\_address@domain.invalid” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> ruby 1.8.6 (2007-09-23) [i686-linux]
> 
> Aborted
> 
> $ ruby --version  
> ruby 1.8.6 (2007-09-23 patchlevel 110) [i686-linux]
> 
> This is a big problem for us, any ideas on how to solve it. Note the  
> seg fault does not always happen in ostruct, although it has happened  
> there numerous times.

of course, reproducing this is difficult, it just does not happen  
everytime or even that often.