From: "Charles S. Wilson" <cwilson@ece.gatech.edu>
To: "Schray, Joerg" <joerg.schray@sap-ag.de>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: B20.1: Fork bug (Win95)
Date: Thu, 24 Jun 1999 08:59:00 -0000 [thread overview]
Message-ID: <37725610.5CA1060A@ece.gatech.edu> (raw)
In-Reply-To: <59357A260E15D311B5A60008C75D353021295C@dbwdfx13.wdf.sap-ag.de>
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
WARNING: multiple messages have this Message-ID
From: "Charles S. Wilson" <cwilson@ece.gatech.edu>
To: "Schray, Joerg" <joerg.schray@sap-ag.de>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: B20.1: Fork bug (Win95)
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <37725610.5CA1060A@ece.gatech.edu> (raw)
Message-ID: <19990630221000.pdaiGLfvXyQ8w_syBfZBlUr9k6tiin0GCDI-ADXt4k0@z> (raw)
In-Reply-To: <59357A260E15D311B5A60008C75D353021295C@dbwdfx13.wdf.sap-ag.de>
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
next prev parent reply other threads:[~1999-06-24 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-23 10:23 Schray, Joerg
1999-06-24 8:59 ` Charles S. Wilson [this message]
1999-06-30 22:10 ` Charles S. Wilson
1999-06-30 22:10 ` Schray, Joerg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37725610.5CA1060A@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=joerg.schray@sap-ag.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).