From: Christian Kaiser <chk@...>
Date: 2004-04-16T23:04:12+09:00
Subject: Re: "bad file descriptor" in Win32 DLL

Kaspar,

because it is at a simple code like

logstring = "#{self.type}: hallo"

and the trace is then:

    'write'
    'type'
    ...

(why does 'type' call write? And why on an invalid descriptor?)

or at a Regexp comparison:

    if sPart =~ "^--(?:[\r\n]|$)" # end of multi-part mail


I get it with a call stack of:

    'write'
    '=~'
    ...

Again, why does '=~' call 'write'? Strange, isn't it?

Christian


"Kaspar Schiess" <eule@space.ch> wrote in message
news:407FE344.3050600@space.ch...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Christian Kaiser wrote:
>
> | Using Ruby 1.81, the DLL (msvcrt-ruby18.dll) sometimes raises an
exception
> | "Bad file descriptor" in "write".
> |
> | The DLL of 1.6.8 (mswin32-ruby16.dll) does not show this behaviour.
> |
> | Is that known, and if yes, how can I get rid of it? Any hints
appreciated.
>
> I get that too, but often because I try to #write to something I cannot
> write to. The error message is not descriptive, but there is often a
cause.
>
> When exactly do you get the message and why do you think you should not
> be getting it ?
>
> kaspar - code philosopher
>
> - -- stolen off the net --
> Ban the bomb.  Save the world for conventional warfare.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFAf+NEFifl4CA0ImQRAtzMAJ9JH6wRoueiiFEecEN2Yk+S1FVCbACeMDcB
> ayV3fiuaJtr89l9Ff+Kwv6w=
> =z+Dy
> -----END PGP SIGNATURE-----
>
>