X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 04 Feb 2008 18:20:03 -0800
From: Jerry DeLisle <jvdelisle AT verizon DOT net>
Subject: Re: Memory leak problem reported with gfortran
In-reply-to: <02fa01c86795$48d202d0$2e08a8c0@CAM.ARTIMI.COM>
To: cygwin AT cygwin DOT com
Message-id: <47A7C7D3.9080302@verizon.net>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
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>  <02fa01c86795$48d202d0$2e08a8c0 AT CAM DOT ARTIMI DOT COM>
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
X-IsSubscribed: yes
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

Dave Korn wrote:
> On 04 February 2008 22:25, 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.
>>
>> Also, in case it isn't clear, Cygwin malloc is just Doug Lea's version
>> of malloc v2.8.3 with very few changes.
>>
>> cgf
> 
>   Since I'm currently building gcc4 to check out some autogen-vs-fixinc
> changes, I'll build fortran as well and take a look at the testcase too.  I'd
> guess that's it's probably a libgfortran problem, since it affects both cygwin
> *and* mingw, but I'll take a look at it under a debugger and see if I can
> help.
> 
Thanks Dave,

I think it is in libgfortran as well.  I am still hunting.  I believe it is 
specific to internal units.  In other words, writing to a character string.  I 
eliminated all other IO operations from the test case and it fails on some sort 
of memory allocation.

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/