Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 7 Aug 2003 13:56:16 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Win2k and cygwin memory leak Message-ID: <20030807175616.GC1689@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Thu, Aug 07, 2003 at 12:52:53PM -0400, Brian DOT Kelly AT empireblue DOT com wrote: >Ah well, someday the denial will end, or the problem will get fixed >unintentionally when some other change is made and the "cygworld will >go on". What a clueless comment. It is not "denial" to assert that an OS which allocates memory and doesn't free it is broken. If cygwin triggers a windows problem that does not mean that it is a cygwin problem no matter how hard that is for you to understand. I fix all sorts of problems in cygwin which are really windows problems but, golly gee, if I can't duplicate them, I can't fix them. And, my willingness to debug some things is limited. If it takes running a perl script every five minutes for a day to duplicate the problem, then that is not something that I'm going to do anytime soon. This is not denial. This is a refusal to take a large amount of my time to find a workaround to a windows problem. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam AT sourceware DOT org and be permanently blocked from mailing lists at sources.redhat.com -- 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/