Bugs item #5339, was opened at 2006-08-07 09:08
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=5339&group_id=426

Category: Core
Group: 1.8.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Sylvain Joyeux (lapinot)
Assigned to: Nobody (None)
Summary: [PATCH] spurious "cross-thread error in rb_thread_schedule" 

Initial Comment:
POSIX dictates that signals are per-process and not per-thread. The problem 
in Ruby is when thread_timer is used: nothing ensures that the signal will 
be caught by the main thread, and I get spurious "cross-thread violations 
in rb_thread_schedule" errors because the signal handler is called in the 
context of the timer thread ...

The "standard" solution is to block all signals in the timer thread


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=5339&group_id=426