From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31700 invoked by alias); 8 Feb 2008 12:13:07 -0000 Received: (qmail 31581 invoked by alias); 8 Feb 2008 12:12:24 -0000 Date: Fri, 08 Feb 2008 12:13:00 -0000 Message-ID: <20080208121224.31580.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libfortran/35063] [Regression wrt g77] I/O leaks handles/memory on Windows XP In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "jpr at csc dot fi" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-02/txt/msg00945.txt.bz2 ------- Comment #24 from jpr at csc dot fi 2008-02-08 12:12 ------- Subject: Re: [Regression wrt g77] I/O leaks handles/memory on Windows XP > This might be desirable for other reasons, but it will not fix the problem > completely. Yeah well, the easy way out here would be to include "__gthread_mutex_destroy" in the gthread-api. This should call CloseHandle() (or a new __gthr_win32_mutex_destroy() with a call to CloseHandle()) for the win32 threads and pthread_mutex_destroy() for the posix threads, etc... and call the new function in a few relevant places in libgfortran... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063