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
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
From:	Andrew DeFaria <ADeFaria AT Salira DOT com>
Subject:	Re: Win2k and cygwin memory leak
Date:	Thu, 07 Aug 2003 11:58:10 -0700
Lines:	42
Message-ID:	<bgu7f9$odl$1@main.gmane.org>
References:	<OF84A14F1C DOT 826AE498-ON85256D7B DOT 00640BE6 AT empirehealthcare DOT com>
Mime-Version:	1.0
X-Complaints-To:	usenet AT main DOT gmane DOT org
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language:	en-us, en, zh
In-Reply-To:	<OF84A14F1C.826AE498-ON85256D7B.00640BE6@empirehealthcare.com>

Brian DOT Kelly AT empireblue DOT com wrote:

> Gosh, isn't there a *win* in *cygwin*?? Not that I'm "demanding" 
> anything or goodness knows, making suggestions about how you 'Oh Great 
> One' should allocate your resources - goodness *no*! But this notion 
> that a WinDoze problem is not *also* a cyg*win* problem - is quite a 
> *CURIOUS* one to this *clueless* simpleton - INDEED!!

Sticking three letters in a name does not make Cygwin == Windows. It is 
the job of the OS to manage memory not the job of the program. When a 
process ends the OS is responsible for cleaning up any of the resources 
that the process aquired. If the OS fails to do this then it's the OS 
that needs to be fixed, not the process.

> Seems in a way that you're saying "I don't care if what I built 
> doesn't work for this or that because it's Microsoft's problem".

Seems like your saying that (using a car analogy) he should replace the 
carberator when the real problem is a leak in the fuel line.  (IOW 
you're attacking the wrong area - your problem lies elsewhere).

> I really don't think you as one who is quick to let Microsoft define 
> what he can and can't do - as you yourself have said

Are you asking Cygwin to re-write and take control of management of 
memory from the OS?!? That's like asking the carberator mechanic to 
build his own fuel line running outside the body of the car!

> So indeed you pick and choose which *Microsoft* problems to fix that 
> keep cyg*win* from working - all along *denying* it's a cyg*win* 
> problem .....

Yes because some problems are fixable or are within the domain of where 
Cygwin has proper control. You can fix a carberator to get extra house 
power but if the main engine only has 2 cyclinders don't ask the 
carberator mechanic to get 8 cyclinder performance - talk to the maker 
of the engine itself!

> Interesting how a 'Great' mind works ;-) .....

Interesting how a clueless mind wanders off...



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