From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10607 invoked by alias); 23 May 2010 07:21:22 -0000 Received: (qmail 10571 invoked by uid 48); 23 May 2010 07:21:20 -0000 Date: Sun, 23 May 2010 07:21:00 -0000 Message-ID: <20100523072120.10570.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libgcj/28263] [win32] Memory Leak In Cleaning Exception Handling Contexts In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: java-prs@gcc.gnu.org From: "ktietz at gcc dot gnu dot org" Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2010-q2/txt/msg00067.txt.bz2 ------- Comment #2 from ktietz at gcc dot gnu dot org 2010-05-23 07:21 ------- (In reply to comment #1) > This issue is solved for mingw-w64 runtime. It uses no more the mingwm10.dll > mechanism. Instead it uses TLS callbacks to implement it. By this reason the > Cleaning of Exception Contexts is always present for this runtime. Maybe > mingw.org's runtime will support TLS callbacks sometimes, too. > This bug remains for Windows OSes without TLS callback support, and for those > the -mthreads build-option can solve the issue. > The mechanism of TLS callback is now present for mingw.org's runtime too. Even the use of mingwm10.dll for OSes (like 9x/Me) is solved. Additional it isn't anymore of importance to link by -mthread option. The cleaning up is effective now anyway. So I close this bug as invalid, as the solution isn't part of gcc itself. -- ktietz at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28263