------- Comment #6 from fxcoudert at gcc dot gnu dot org 2008-02-04 23:40
-------
(In reply to comment #2)
> I have confirmed this under cygwin. Taking the READ statement out so the
> program can run unabated, leads to a system failure trying to allocate
> memory.
> This is platform specific, the program runs to completion on linux with no
> problems.
What's weird is that the number of "Handles" get bigger even though the "Mem
usage" of the application actually doesn't grow (for me, it's fixed at 860 K).
I've debugged it a bit: of malloc/calloc/realloc, only malloc is called, and
always from libgfortran's get_mem. Having adding output statements to get_mem()
and free_mem(), I've checked that all allocations are deallocated soon after.
Maybe that's the result of some alloca'ed memory? (shooting in the dark,
really)
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fxcoudert at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
