X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <47A614EC DOT 1010104 AT verizon DOT net> Subject: RE: Memory leak problem reported with gfortran Date: Sun, 3 Feb 2008 21:57:40 -0000 Message-ID: <01bc01c866af$cbe52080$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <47A614EC.1010104@verizon.net> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 03 February 2008 19:24, Jerry DeLisle wrote: > I have confirmed this problem on Cygwin reported here: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063 > Those of you most familiar with the Windows environment could perhaps help > here. Is this a bug in Cygwin memory management? Are you using cygwin as anything other than a shell to launch mingw32 compilers and the mingw32 applications they build? 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/