> -----Original Message-----
> From: Brent Roman [mailto:brent / mbari.org] 
> Sent: Monday, May 21, 2007 5:19 PM
> To: ruby-core / ruby-lang.org
> Subject: Segmentation Fault in GC
> 
> 
> Help!
> 
> Our Ruby controlled Robotic Marine Laboratory started failing 
> with segmentation faults just a few days before it was to be 
> deployed.  We had seen random, very occasional segmentation 
> faults for some months, as our application grew larger and 
> more complex.  Then, just days before the ship was scheduled 
> to sail, after we'd integrated a couple new and exciting 
> features, we started getting segfaults regularly.
> 
> We have not been able to correlate the fault to a particular 
> operation in our application.  However, it never occurs 
> sooner than 30 minutes or so after the application starts.  
> The application is heavily multithreaded and uses 3 RS-232 
> serial ports accessed via the ruby termios library.
> 
> Can anyone give me any hints as to what's going on by
> looking at the attached stack backtrace?
> 
> It appears to be deep into a GC cycle while executing Marshal.dump.
> 
> Some notes on the target environment:
>     ARM9 processor (ep9312) running Linux kernel v2.4.26
>     (cross-)Compiled with gcc version 3.4.5  -Os  (not omitting
> framepointer!)
>     glibc 2.2.5
>     Ruby 1.6.8

<snip>

Whoa, what? You're using 1.6.8? Seriously consider an upgrade to 1.8.6.
The 1.6.x branch is dead, and much less reliable than the 1.8.x branch.
Please consider upgrading asap.

Regards,

Dan


This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful.  If you have received this communication 
in error, please immediately notify the sender by reply e-mail and destroy 
all copies of the communication and any attachments.