--- Comment #13 from jpr at csc dot fi 2008-02-07 05:07 ---
Subject: Re: I/O leaks handles/memory on Windows XP
>
> --- Comment #12 from tkoenig at gcc dot gnu dot org 2008-02-06
21:49 ---
> Just wondering... is this a regression?
At least g77 runs the two examples (in comm
--- Comment #12 from tkoenig at gcc dot gnu dot org 2008-02-06 21:49
---
Just wondering... is this a regression?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
--- Comment #11 from jpr at csc dot fi 2008-02-06 20:54 ---
Subject: Re: I/O leaks handles/memory on Windows XP
I had a look: the problem seems to be with the logic of mutex->counter in
gcc/config/i386/gthr-win32.c. Libgfortran makes the following calls
during an internal write
1)
--- Comment #10 from Jerry_V_DeLisle at rl dot gov 2008-02-06 20:25 ---
Reply to comment #9:
This is a very important observation. I have checked the code and we have code
that free's the internal unit (free_internal_unit) and I have confirmed that it
is called correctly after every wr
--- Comment #9 from jpr at csc dot fi 2008-02-06 11:31 ---
Subject: Re: I/O leaks handles/memory on Windows XP
just an observation: if i build gcc with "thread model=single", all seems
well.
Juha
>
>
> --- Comment #8 from jvdelisle at gcc dot gnu dot org 2008-02-06 01:27
> --
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2008-02-06 01:27
---
I will work this one. I think the problem is not in freeing, but in not
reusing a UNIT structure already open.
--
jvdelisle at gcc dot gnu dot org changed:
What|Removed |Ad
--- Comment #7 from fxcoudert at gcc dot gnu dot org 2008-02-05 10:55
---
OK, found it by commenting out various parts of the I/O library until it
disappeared. The leak is the following line in data_transfer_init (transfer.c):
dtp->u.p.current_unit = get_unit (dtp, 1);
The memory
