From: Mike Boone <boonedocks@...>
Date: 2008-01-03T06:00:03+09:00
Subject: Re: Ruby bug reading from /dev/urandom after failed require?

On Dec 22 2007, 10:47 am, Yukihiro Matsumoto <m...@ruby-lang.org>
wrote:
> The bug must lie between Cygwin and Ruby.  We don't call lseek
> explicitly.  You can clearly see this by doing strace on Linux (or
> other platforms), which don't call lseek at all.  So, someone (in the
> library, I guess) must call lseek weirdly on Cygwin.
>
> I have no clue right now to identify "someone".

Sorry for the late reply. I have done some more experimentation with
the Ruby source in Cygwin.

The current Ruby 1.8.6 does not make in Cygwin, giving an error about
strftime.o. However, the stable-snapshot does make correctly, but my
test script still gives the /dev/urandom error. Interestingly,
compiling Ruby 1.9.0 works fine and the /dev/urandom error goes away.

I have GDB on my Cygwin system, but I am not sure where to begin
tracing the problem. Where would be the best place to set a breakpoint
for tracking the error "No such file or directory - /dev/urandom"?

Thanks,
Mike Boone
http://boonedocks.net/mike/