Comment 28 for bug 520715

Well, a good start would be to reproduce the issue, analyze how ruby1.8 is using pthreads, and see if you can either produce a test case without ruby (to be able to find a specific bug or change in eglibc), or understand what ruby is doing with pthreads and fix it.