X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Sun, 03 Feb 2008 11:24:28 -0800
From:	Jerry DeLisle <jvdelisle AT verizon DOT net>
Subject:	Memory leak problem reported with gfortran
To:	cygwin AT cygwin DOT com
Message-id:	<47A614EC.1010104@verizon.net>
MIME-version:	1.0
User-Agent:	Thunderbird 2.0.0.9 (X11/20071115)
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

I have confirmed this problem on Cygwin reported here:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063

I am not very familiar with the windows environment.  Having patched most of the 
gfortran I/O library in the last 2-3 years I can say that we do a lot of memory 
allocation for I/O.

On Linux based systems we do not see any issues (checked with valgrind).  This 
problem acts like a failure to free memory.  I do not know what is meant by the 
term "handle" other than a pointer to an allocated block of memory.

Those of you most familiar with the Windows environment could perhaps help here. 
    Is this a bug in Cygwin memory management?

I will be happy to provide additional information as soon as I know what is 
pertinent.

I have latest Cygwin as of about two weeks ago and I can provide a gfortran 
binary if needed.

Regards,

Jerry

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