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="iso-8859-1"
From: pullmoll AT t-online DOT de (Juergen Buchmueller)
Reply-To: pullmoll AT stop1984 DOT com
To: cygwin AT cygwin DOT com
Subject: Gotcha, /dev/urandom (was Re: _exit() missing WSACleanup() call?)
Date: Thu, 8 Aug 2002 18:04:04 +0200
User-Agent: KMail/1.4.2
References: <1028578338 DOT 7433 DOT ezmlm AT cygwin DOT com> <017301c23d6f$0033bc90$6132bc3e AT BABEL> <01db01c23dfe$d4d4d260$6132bc3e AT BABEL>
In-Reply-To: <01db01c23dfe$d4d4d260$6132bc3e@BABEL>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200208081804.20387.pullmoll@stop1984.com>

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

On Wednesday 07 August 2002 12:40, Conrad Scott wrote:
> As it happens, all the distractions flew away and this is now
> fixed in CVS.

I already sent me my thank you privately. And now I can ease Corinna's life, 
too, because I must excuse myself for suspecting a problem in mmap(). I was 
wrong, because mmap() seems to work perfectly fine.

The problem I have with loosing memory on Win98SE happens when I repeatedly 
fopen/fread/fclose the device /dev/urandom. Everytime I do this I loose a 
good chunk of memory, which only by accident was about the same size as my 
mmap()ed region and thus led me to search in the wrong place.

For now I can deal with it by opening /dev/urandom only once in the parent and 
using the duplicated filehandle in the child processes (I hope this will fix 
it - not yet done), but someone should inspect the code there to see where 
the memory leak is.

> // Conrad

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

iD8DBQE9UpaBtCKWJo++MqgRAjZqAJ99n2crTjuH/l+S1h+y2HRc2I0xJwCg0G/I
tKVuTexHUKTi2dXgmS/oBh0=
=bcOU
-----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/