public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/28263] [win32] Memory Leak In Cleaning Exception Handling Contexts
Date: Sun, 23 May 2010 07:21:00 -0000 [thread overview]
Message-ID: <20100523072120.10570.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28263-8271@http.gcc.gnu.org/bugzilla/>
------- 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
prev parent reply other threads:[~2010-05-23 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 2:03 [Bug libgcj/28263] New: " rmathew at gcc dot gnu dot org
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 [this message]
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=20100523072120.10570.qmail@sourceware.org \
--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).