# Facing Segmentation Fault

**URL:** <https://www.ruby-forum.com/t/facing-segmentation-fault/143721>\
**Category:** Ruby\
**Created:** [July 22, 2008, 7:20am UTC](https://www.ruby-forum.com/t/facing-segmentation-fault/143721 "2008-07-22T07:20:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![darshana](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/53a042/32.png) [@darshana](https://www.ruby-forum.com/u/darshana)\
**Post date:** [July 22, 2008, 7:20am UTC](https://www.ruby-forum.com/t/facing-segmentation-fault/143721/1 "2008-07-22T07:20:50Z")

</div>

Hi All,

We are working on project running ruby 1.8.5 on UNIX.

We have been getting segmentation faults [BUG] fairly consistently (but  
at unpredictable times)  
If anyone faced this kind of issue before or anyone can provide  
pointers, it will be very helpful.

Regards  
Darshana

---

<div class="post-metadata">

**Author:** ![darshana](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/53a042/32.png) [@darshana](https://www.ruby-forum.com/u/darshana)\
**Post date:** [July 22, 2008, 7:27am UTC](https://www.ruby-forum.com/t/facing-segmentation-fault/143721/2 "2008-07-22T07:27:10Z")

</div>

On Tue, 2008-07-22 at 14:15 +0900, Darshana G. wrote:

> Regards  
> Darshana

If you have gdb, disable the ulimit on core dump files. Then when you  
get a segfault, go into the core dump with gdb, do a stack backtrace and  
file a bug report. Given a stack backtrace, it shouldn’t take them too  
long to find it.

## If you can, upgrade to 1.8.6. 1.8.5 is not supported any more.

M. Edward (Ed) Borasky  
[ruby-perspectives.blogspot.com](http://ruby-perspectives.blogspot.com)

“A mathematician is a machine for turning coffee into theorems.” –  
Alfréd Rényi via Paul Erdős