From: Nasir Khan <rubylearner@...>
Date: 2007-06-24T11:32:52+09:00
Subject: Signal handling problem in ruby

------=_Part_138601_1088449.1182652373872
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/220937

I presume I am running into similar problem but this time with ruby
1.8.6(2007-03-13 patchlevel 0) [i386-mswin32] (under windows).
Basically my program runs and spawns several threads, some of which block on
network IO but the main thread after doing all initialization etc installs a
signal handler   by trap("INT") { s.stop }  where stop() is a method call to
stop processing.

The ^c signal is not delivered to the program until I send a network message
(unblocks the different thread waiting for IO).

Is this issue seen by others on 1.8.6? Any pointers are appreciated.

TIA
- nasir

------=_Part_138601_1088449.1182652373872--