This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
FW: Memory leak problem reported with gfortran
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "Thread TITTTL'd!" <cygwin-talk at cygwin dot com>
- Date: Thu, 7 Feb 2008 14:48:22 -0000
- Subject: FW: Memory leak problem reported with gfortran
- Reply-to: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk at cygwin dot com>
On 06 February 2008 09:22, Corinna Vinschen wrote:
> 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
I'll bet that's the first time our heap limitations have helped *solve* a
bug! :)
cheers,
DaveK
--
Can't think of a witty .sigline today....