rubinius/rubinius — pull request #1935 by ryoqun (2012-09-29 02:45:13+00:00)
Title: Fix newly-introduced Thread#kill deadlock

The following commit introduced another deadlock. Threads MUST be
Rubinius.synchronize-d, but they weren't in Thread#kill.

ba7667b0ab28a6f9fb5b3a966d9ab32ea79318ed Correctly implement Thread#kill

Previously, Thread#kill internally used Thread#raise, which had gotten
completely deadlock-free. And there is no problem.

But, the commit made Thread#kill use a primitive for its function. That must be
inside Rubinius.synchronize as was before.