From: Masao M. <mu...@hi...> - 2005-10-06 18:38:09
|
Hi, I've trid to fix this problem, and it seems to work now. I hope someone try the CVS version of Ruby/GLib and report the bugs. # I'm sorry to be late. On Mon, 1 Aug 2005 16:46:22 +0200 Bram Senders <br...@lu...> wrote: > Hi there, > > The Ruby GLib mainloop bindings are giving me some trouble in > combination with Ruby's signal handling. When I have a very simple > app, like: > > -------- > require 'glib2' > > mainloop = GLib::MainLoop.new(nil, true) > > mainloop.run > -------- > > I can only kill this by sending it SIGKILL. Even when I add a signal > handler to properly call mainloop.quit: > > -------- > require 'glib2' > > mainloop = GLib::MainLoop.new(nil, true) > > ['INT', 'TERM', 'QUIT'].each do |sig| > Signal.trap(sig) { puts "Going to quit"; mainloop.quit } > end > > mainloop.run > -------- > > Here also the signal handler is not called, and the only way to kill > this program is using SIGKILL. > > I hope someone can help me to solve this. > > TIA, > > Bram Senders > > > Please Cc me when replying to the list. > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > ruby-gnome2-devel-en mailing list > rub...@li... > https://lists.sourceforge.net/lists/listinfo/ruby-gnome2-devel-en > -- -- .:% Masao Mutoh<mu...@hi...> |