Re: B20.1: Fork bug (Win95)

["Charles S. Wilson" <cwilson@ece.gatech.edu>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]

Jörg -

>
> I searched the mailing list for similar bug reports and found the thread
> "dll + fork", where a bug with dynamic loading was reported. I suspect
> that the way cygwin1.dll implements gethostbyname is via delegation to a
> windows DLL, so that this bug isn't anything new. However, it shows that
> even calls to the published Cygwin API can fail in connection with fork
> under Win95.
>
> I found the bug running the perl regression tests tracking down a failure
> of lib/io_sock.t (perl5.005_03 compiled statically).

Out of curiosity, were you using the "my" patchkit from
ftp://belgarion.resnet.gatech.edu (old location) or
http://cygutils.netpedia.net (new location) to build perl? If not, you might
want to try it. There are two versions - one for static builds and one for
dynamic builds. The dynamic build patchkit is more recent, and contains a
dirty little hack to io_sock.t that works around the problem, but doesn't
actually fix it. You might try incorporating the changes to io_sock.t from the
dynamic build patchkit into your build tree. You are correct, thought, that
the error seems to be due to the dll forking problem. It would be better, of
course, to fix cygwin.

I believe (without any supporting evidence) that the dll+fork problem will be
fixed in B21. Is this correct, cygwin-list-people?

--Chuck



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com