This is the mail archive of the
cygwin-developers@sources.redhat.com
mailing list for the Cygwin project.
Re: small problem with exec
- To: cygwin-developers at sources dot redhat dot com
- Subject: Re: small problem with exec
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Mon, 25 Sep 2000 20:53:27 -0400
- Reply-To: cygwin-developers at sources dot redhat dot com
Egor Duda wrote:
>exec() inherits open file handles, and some of them can possibly be
>sockets. cygwin has global variable to track the number of open
>sockets (number_of_sockets) which increments when socket is
>created and decrements when socket gets freed. after fork this
>variable is initialized properly, but after exec it is 0. when exec'ed
>process closes socket, cygwin prints "socket count < 0" warning.
>
>should number_of_sockets be eliminated or passed in child_info_spawn?
It should be eliminated. The dynamic loading of winsock functions eliminated
the need for this some time ago. I actually thought I got rid of this already.
It's gone now at least.
Thanks for catching this. I am surprised that I haven't noticed the error message
that you noted.
cgf