X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 6 Feb 2008 10:21:54 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Memory leak problem reported with gfortran
Message-ID: <20080206092154.GP5866@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <47A614EC DOT 1010104 AT verizon DOT net> <20080204103512 DOT GA5866 AT calimero DOT vinschen DOT de> <47A782C7 DOT 3060501 AT verizon DOT net> <20080204222455 DOT GA3058 AT ednor DOT casa DOT cgf DOT cx> <20080205103104 DOT GK5866 AT calimero DOT vinschen DOT de> <47A90C18 DOT 1070709 AT verizon DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <47A90C18.1070709@verizon.net>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Feb  5 17:23, Jerry DeLisle wrote:
> Corinna Vinschen wrote:
>> On Feb  4 17:24, Christopher Faylor wrote:
>>> On Mon, Feb 04, 2008 at 01:25:27PM -0800, Jerry DeLisle wrote:
>>>> The test also appears very clean on Linux.  The gfortran library is
>>>> implemented in C.  I need to examine some dumps from the compiler and I
>>>> will get back with you off list if I don't spot the problem.
>>> I am fairly certain that Corinna would want to keep any correspondence
>>> on-list.
>> Yup, that's right.
>
> OK, we have isolated the problem now.  Confirming its in the libgfortran.  
> The reason we did not see it on Linux is because we just did not run out of 
> memory yet and when the test program completes, it does actually free what 
> was allocated.  We are failing to reuse an already allocated block so we 
> were allocating a new one for every single WRITE to the string.
>
> Thanks for all your help.

Thanks for letting us know.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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