From: Laurent Julliard <laurent@...>
Date: 2004-11-20T06:20:40+09:00
Subject: Re: [Q] Bug in Process.kill on win32?

Daniel Berger wrote:

>>Well the point is that even when I use SIGINT (either using the string 
>>"SIGINT" or "INT" or the numeric value 2) it still gives the exact 
>>same error.
> 
> 
> Ah, you are correct.  That's a bug in the installer it looks like. 
> Your other option is to build from source and see if you still see the
> same error.
> 

Unfortunately I don't have Visual Studio available and cannot 
recompile. This being said I wouild really like to be able to fix this 
in the Ruby code. It must be an obvious bug in the win32.c file but I 
don't know the win32 interface well enough to see it


> 
> I don't define SIGINT or SIGKILL in win32-process, but I could easily
> enough.  Also note that SIGINT probably isn't going to work they way
> you think it should.  This has to do with restrictions on sending
> signals to Windows processes, depenind on how those processes were
> created.
> 
> However, I think I know how to make it work the way most folks would
> expect.  I'll work on that in the coming weeks.
> 

That would be great!! But the only thing I need is to be able to send 
a signal to a remote process that I can trap. using SIGINT seems the 
obvious choice on Unix/Linux and I was hoping that it would work the 
same on Windows.

Another thing that would be great is that you port the park Heesob 
popen call as well in addition to open3. I can;t use the standard 
popen call with win32 utils because the pid arrays are different as 
you know.

Thanks for your help!

Laurent

-- 
Laurent JULLIARD
http://www.moldus.org/~laurent