If you are running your Ruby code on MRI (the official implementation) there is no way to make your Ruby code any threadsafer. They have global interpreter lock in place.
Segfaults generally don't cause by Ruby code, and when it does it is a bug of the interpreter itself. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/2c5fea73-2f03-4d82-b3db-2dc8dcd0b38b%40googlegroups.com.
