From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32670 invoked by alias); 5 Jul 2006 02:03:08 -0000 Received: (qmail 32553 invoked by uid 48); 5 Jul 2006 02:03:07 -0000 Date: Wed, 05 Jul 2006 02:03:00 -0000 Subject: [Bug libgcj/28263] New: [win32] Memory Leak In Cleaning Exception Handling Contexts X-Bugzilla-Reason: CC Message-ID: Reply-To: gcc-bugzilla@gcc.gnu.org To: java-prs@gcc.gnu.org From: "rmathew at gcc dot gnu dot org" Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2006-q3/txt/msg00025.txt.bz2 List-Id: There is a leak of 24 bytes of exception handling context per Java thread on MinGW due to a hack that fools the MinGW runtime into thinking that multi-threaded exception handling is in effect but avoids linking to the correct __mingwthr_key_dtor() from mingwm10.dll and instead links to a dummy version from libmingw32.a. See also: http://gcc.gnu.org/ml/java/2003-04/msg00046.html http://gcc.gnu.org/ml/java/2006-07/msg00014.html http://gcc.gnu.org/ml/java/2006-07/msg00017.html A workaround for avoiding this leak is to explicitly use -mthreads while linking Java programmes with GCJ. -- Summary: [win32] Memory Leak In Cleaning Exception Handling Contexts Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rmathew at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-mingw32 GCC target triplet: i686-pc-mingw32 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28263