This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/35063] [Regression wrt g77] I/O leaks handles/memory on Windows XP
- From: "jpr at csc dot fi" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Feb 2008 05:29:14 -0000
- Subject: [Bug libfortran/35063] [Regression wrt g77] I/O leaks handles/memory on Windows XP
- References: <bug-35063-12481@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #22 from jpr at csc dot fi 2008-02-08 05:29 -------
Subject: Re: [Regression wrt g77] I/O leaks handles/memory
on Windows XP
> So if the above is really at fault then the
> leak should not manifest on Cygwin at all.
The logic there is ok i guess, as i already noted later in the thread.
As the handles also leak using posix threads under cygwin, i guess the
posix thread implementation does something similiar. The problem is that
when the mutex is done with pthread_mutex_destroy() should be called.
gcc's gthread interface used in libfortran however does not however have
this functionality as far as i can tell from the sources.
Anyway, Jerry idea of reusing the internal unit structure would
effectively solve this problem, being also a good thing otherwise IMO.
Juha
> This gthr-win32 stuff should only be run if --enable-threads=win32.
> That is not the case with Cygwin which should be using pthreads
> (--enable-threads=posix). So if the above is really at fault then the
> leak should not manifest on Cygwin at all.
>
> Brian
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063