Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Content-Type: text/plain;
  charset="us-ascii"
From: pullmoll AT t-online DOT de (Juergen Buchmueller)
Reply-To: pullmoll AT stop1984 DOT com
To: cygwin AT cygwin DOT com
Subject: No WSACleanup() call ind _exit()?
Date: Mon, 5 Aug 2002 17:40:32 +0200
User-Agent: KMail/1.4.2
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200208051740.40056.pullmoll@stop1984.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi developers,

I have serious trouble with a project which I'm trying to port to CYGWIN. This
project makes heavy use of fork() (actually fork2() to detach from the init
process) and child processes' file handles are almost always sockets.

Now I read that CYGWIN handles this case by silentrly calling WSAStartup() for
every child that inherits a socket handle - but the CYGWIN libc
implementation does not seem to call WSACleanup() during the _exit() function
cleanup in that case?

The effect is that after a few minutes, after maybe 100 child processes were
forked and exited again, Windows does something on a severity scale between
displaying message boxes about a lack of resources to hard lockups with
faults in 'kernel32.dll'. I'm lost.

I tried to WSACleanup() in my user osd_exit() function to no avail. My best
guess is that there are other resources which I cannot give free this way?

The same project runs fine for days on various FreeBSD and GNU/Linux systems.

I also tried to find something related in the cygwin DLL source code and only
saw that there is no obvious WSACleanup() call somewhere.

Ciao,
Juergen Buchmueller
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE9Tpx2tCKWJo++MqgRAsk/AJ9s5saSRr9ulFuBuorN/b0ub9Z71ACg0lot
N3/b9w4D8ZLojj64gB8upGE=
=ndbL
-----END PGP SIGNATURE-----


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/