> -----Original Message-----
> From: U.Nakamura [mailto:usa / garbagecollect.jp] 
> Sent: Tuesday, January 04, 2005 6:21 PM
> To: ruby-core / ruby-lang.org
> Subject: Re: [BUG] Win32: rb_sys_fail() - errno == 0
> 
> 
> Hello,
> 
> In message "Re: [BUG] Win32: rb_sys_fail() - errno == 0"
>     on Jan.04,2005 03:57:22, <Daniel.Berger / qwest.com> wrote:
> | > | Although Florian's original code seems to work fine, I
> | > still see this
> | > | error in win32-process when I attempt to use 
> rb_sys_fail(0) in the
> | > | Process.kill code.
> | > 
> | > How should I do to reproduce the bug?
> | 
> | Download win32-process-0.3.1
> | 
> | Modify process.c, and replace the rb_raise() functions with
> | rb_sys_fail(0) in the process_kill() function.  You should 
> see where 
> | I've commented them out.
> 
> Hmm, is the point here?
> 
> process.c:95:    
> rb_raise(rb_eStandardError,ErrorDescription(GetLastError()));
> process.c:96:    //rb_sys_fail(0);
> 
> If so, it's not ruby's problem.
> Because there are no ruby API call before here. Isn't it?
> 
> 
> Regards,
> -- 
> U.Nakamura <usa / garbagecollect.jp>

I'm not sure I follow, because this has worked as expected in certain
circumstances in the past (i.e. it raised Errno::ENOENT).

Perhaps I need more detail on how rb_sys_fail() actually works.  That,
or I need to figure out a way to explicitly raise Errno::ENOENT within a
C extension.

Regards,

Dan