win32-process 0.4.0 - SIGINT/SIGBRK not working

> -----Original Message-----
> From: win32utils-devel-bouncesrubyforge.org 
> [mailto:win32utils-devel-bouncesrubyforge.org] On Behalf Of

> Luis Lavena
> Sent: Friday, May 12, 2006 11:16 AM
> To: win32utils-develrubyforge.org
> Subject: [Win32utils-devel] win32-process 0.4.0 - 
> SIGINT/SIGBRK not working

<snip>

> now, from a irb console I tried the following:
> 
> irb(main):001:0> require 'win32/process'
> => true
> irb(main):002:0> Process.kill("SIGBRK",
3380)
> NameError: uninitialized constant
Process::CTRL_BRK_EVENT
>         from 
>
C:/Ruby/lib/ruby/gems/1.8/gems/win32-process-0.4.0-mswin32/l
ib
> /win32/process.rb:156:in
> `kill'
>         from 
>
C:/Ruby/lib/ruby/gems/1.8/gems/win32-process-0.4.0-mswin32/l
ib
> /win32/process.rb:124:in
> `kill'
>         from (irb):2
> irb(main):003:0>

<snip>

Whoops, I'll fix that in the next release.  Just need to
include the
appropriate module from windows-pr.

> According to MSDN docs, you only could send the 
> GenerateConsoleCtrlEvent to descent process created
with the 
> CREATE_NEW_PROCESS_GROUP

<snip>

Yes, I already know that.  It's documented in the README.

> So there isn't a functional way to send a INT or BRK
signal 
> from other process already created, only the ones
attached to 
> the current console and created with
CREATE_NEW_PROCESS_GROUP
> 
> Couldn't find a workaround, Dan?

I'm certainly open to suggestions.  How does Ruby's
trap("INT") work on
Windows, for example?

Regards,

Dan


This communication is the property of Qwest and may contain
confidential or
privileged information. Unauthorized use of this
communication is strictly 
prohibited and may be unlawful.  If you have received this
communication 
in error, please immediately notify the sender by reply
e-mail and destroy 
all copies of the communication and any attachments.

_______________________________________________
win32utils-devel mailing list
win32utils-develrubyforge.org
http://rubyforge.org/mailman/listinfo/win32utils-devel