public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rmathew at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/28263]  New: [win32] Memory Leak In Cleaning Exception Handling Contexts
Date: Wed, 05 Jul 2006 02:03:00 -0000	[thread overview]
Message-ID: <bug-28263-8271@http.gcc.gnu.org/bugzilla/> (raw)

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


             reply	other threads:[~2006-07-05  2:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05  2:03 rmathew at gcc dot gnu dot org [this message]
2009-09-03  9:24 ` [Bug libgcj/28263] " ktietz at gcc dot gnu dot org
2010-05-23  7:21 ` ktietz at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-28263-8271@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).