Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
X-Originating-IP: [63.203.232.106]
Reply-To: aek@pumpkininc.com
From: "Andrew Kalman" <aektravel@hotmail.com>
To: cygwin@cygwin.com, aek@pumpkininc.com
Subject: Re: vfork problems on Win98 -- is there a fix?
Date: Tue, 11 Sep 2001 10:38:21 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F330YKpDS7hx27kBncc0000f8e7@hotmail.com>
X-OriginalArrivalTime: 11 Sep 2001 17:38:21.0649 (UTC) FILETIME=[8D0F2C10:01C13AE8]

Hi Christopher.

Re:

>I have never seen anything remotely like this on Windows 2000.  I use
>it extensively.
>
>This is YA reason for someone who is having to problem to debug it.

As I mentioned in my previous post, the detailed test that I did was under 
Win2000 SP2, and it showed a memory leak that led to failure after 1 hour.

When I have some time, I will attempt to reproduce the problem entirely 
within the Cygwin environment -- i.e. without my "external" compiler and 
librarian. Should it again display the same problems, I will post the 
makefile to the group so that someone more capable than I can look at it.

For now, the most expedious solution for me is to simply add RAM to the 
machine in question and hope that the make will succeed.

For now, over and out, and thank you for your comments.

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

