delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/01/30/06:27:28

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: memory leaks in fork(?)
Date: Fri, 30 Jan 2004 11:26:33 -0000
MIME-Version: 1.0
In-Reply-To: <NUTMEGqR77bieLYCT4a00000079@NUTMEG.CAM.ARTIMI.COM>
Message-ID: <NUTMEGhbq8rIygHhGWi0000007a@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 30 Jan 2004 11:26:34.0031 (UTC) FILETIME=[EA7B0BF0:01C3E723]

 

> -----Original Message-----
> From: cygwin-owner On Behalf Of Dave Korn

>   I can confirm that there are definitely memory management 
> problems in Agnitum outpost. [...SNIP!...]


Heh, let me just make the implications of that last post explicit:  In reply
to the original poster, I regularly use huge build/configure/make stuff on
my install of cygwin under XP, and I have no such problems; so I suggest
that the problem is not a cygwin bug but something else on your machine that
is causing problems for cygwin.


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019