The Windows socket code in 1.7 aborts with [BUG] everytime winsock
sets an error or warning message. This used to raise an exception. The
problem is known, some discussion was started, but in the end I didn't
see anybody fixing it :(

It's been a while since I posted a message via NNTP, so please tell me
if I'm doing something wrong :)

Danny
http://froukepc.dhs.org/rudl/On Fri, 27 Sep 2002 17:08:42 GMT, Patrick
Bennett <patrick / thebennetts.com> wrote:

>I'm periodically getting these [BUG] errors (not catchable) and I never 
>received a reply to my last post.
>Is this a known problem, and is there a fix available?
>This is with 1.7.2 on W2k (WindowsInstaller build)
>
>Failed: Bad file descriptor
>ERROR P4NotifyD: Caught Errno::EBADF: Bad file descriptor
>        D:/P4Scripts/lib/ruby/1.7/net/protocol.rb:501:in `sysread'
>        D:/P4Scripts/lib/ruby/1.7/net/protocol.rb:501:in `rbuf_fill'
>        D:/P4Scripts/lib/ruby/1.7/net/protocol.rb:477:in `readuntil'
>        D:/P4Scripts/lib/ruby/1.7/net/protocol.rb:488:in `readline'
>        D:/P4Scripts/lib/ruby/1.7/net/smtp.rb:425:in `read_reply'
>        D:/P4Scripts/lib/ruby/1.7/net/smtp.rb:403:in `get_reply'
>        D:/P4Scripts/lib/ruby/1.7/net/protocol.rb:320:in `check_reply'
>D:/P4Scripts/lib/ruby/1.7/net/protocol.rb:576: [BUG] rb_sys_fail() - 
>errno == 0 ruby 1.7.2 (2002-07-02) [i386-mswin32]
>
>