Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
X-Originating-IP:	[63.203.232.106]
Reply-To:	aek AT pumpkininc DOT com
From:	"Andrew Kalman" <aektravel AT hotmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: vfork problems on Win98 -- is there a fix?
Date:	Sat, 08 Sep 2001 23:23:01 -0700
Mime-Version:	1.0
Message-ID:	<F33Zw9i0EozCNIk6cbg0000c75a@hotmail.com>
X-OriginalArrivalTime:	09 Sep 2001 06:23:01.0518 (UTC) FILETIME=[E05A5AE0:01C138F7]

Hi Christopher.

Re:
>If this is important to you then you could build debugging versions of
>make and the cygwin DLL and figure out where the memory was being
>consumed.  Trying to track down where memory leaks occur is always very
>tricky but maybe you could put some checks in cygwin's fork and
>spawn_guts routines as a first step.

Unfortunately, this sort of thing is _way_ beyond my abilities. I don't know 
the first thing about Unix programming.

But I'm puzzled -- if this is a bona fide leak in the Cygwin stuff, then why 
isn't there a major effort to eliminate it? I don't think what I'm using the 
Cygwin bash shell for is all that out of the ordinary ...


--------------------------
Andrew E. Kalman, Ph.D.  aek AT pumpkininc DOT com


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


--
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/

- Raw text -