From: "phasis68 (Heesob Park)" <phasis@...>
Date: 2012-03-19T18:08:45+09:00
Subject: [ruby-core:43464] [ruby-trunk - Bug #6131] Ctrl-C handler do not work from exec process (Windows)


Issue #6131 has been updated by phasis68 (Heesob Park).


As you may know, this bug is due to the Revision r34387.

If the CREATE_NEW_PROCESS_GROUP flag is specified in a call to the CreateProcess function, CTRL+C signal is disabled for all processes within the new process group.

I think r34387 is better to be reverted for compatibility with existing applications.
----------------------------------------
Bug #6131: Ctrl-C handler do not work from exec process (Windows)
https://bugs.ruby-lang.org/issues/6131#change-24934

Author: luislavena (Luis Lavena)
Status: Assigned
Priority: Normal
Assignee: usa (Usaku NAKAMURA)
Category: core
Target version: 1.9.3
ruby -v: ruby 1.9.3-p155 (2012-03-03) [i386-mingw32]


Hello,

Originally reported to TheCodeShop group: https://groups.google.com/forum/?fromgroups#!topic/thecodeshop/ZI9FY-RKYgs

The usage of "rails server" uses `exec` to spawn another process to run a server, and that process do not handle Ctrl-C.

Script to recreate this issue:

https://gist.github.com/2009356

=begin a.rb
trap(:INT) do
  puts "Hit Ctrl+C in a.rb"
end

exec "ruby b.rb"
=end

=begin b.rb
trap(:INT) do
puts "Hit Ctrl+C in b.rb"
exit(false)
end

sleep
=end

Invoking b directly from command line works, but from a.rb it fails to respond to Ctrl-C



-- 
http://bugs.ruby-lang.org/