> If you are man enough to compile from source on your own already, then 
> at least report your GCC and Glibc version as well. It won't be a 
> guaranteed reply, because not everyone will have enough knowledge about 
> glibc inner workings to know when pointers are invalid (or about the 
> ruby code per se, although there are quite some smart enough to 
> understand the C code of the inner ruby-c)

Well, I updated my gcc package and all is well now.


> Noone forces you to use 1.9.x when you are NEW to ruby. Quite the 
> opposite - if you are new to ruby, use 1.8.x and learn it. Being "buggy" 
> is relative - ruby 1.6.x was probably "buggier" than 1.8.x and even 
> within the 1.8.x series you had some releases with a bit more bugs than 
> others.
> 
> If you require stability, use 1.8.x.

Well, considering that 1.9 is so much quicker than 1.8, I opted for 1.8. 
No point in learning a new language if I'm going to run an "older" 
version that is slower than the "new" release.
-- 
Posted via http://www.ruby-forum.com/.