X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-YMail-OSG: It3MViQVM1lBcsF185jKGXCEXOC9.N9LEwQFk7r..KtqHgbZ577U3D00vLzTzbfcU.K6N.Tf63C7YtHgm5A0SEBasN5J6qYZBhLy X-Yahoo-Newman-Property: ymail-3 Message-ID: <47A6319D.7020303@sbcglobal.net> Date: Sun, 03 Feb 2008 21:26:53 +0000 From: Greg Chicares User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Memory leak problem reported with gfortran References: <47A614EC DOT 1010104 AT verizon DOT net> In-Reply-To: <47A614EC.1010104@verizon.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 On 2008-02-03 19:24Z, Jerry DeLisle wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063 [...] > Is this a bug in Cygwin memory management? According to this report (marked in bugzilla as a duplicate): http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35064 a similar problem was observed with MinGW. Could it be an issue with the msw port of gfortran, rather than a problem with Cygwin's or MinGW's memory-management system routines? -- 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/