From: Erik Groeneveld <erik@cq2.nl>
To: Andrew Haley <aph@redhat.com>
Cc: "Boehm, Hans" <hans.boehm@hp.com>, "java@gcc.gnu.org" <java@gcc.gnu.org>
Subject: Re: GC leaks debugging
Date: Thu, 14 Apr 2011 08:36:00 -0000 [thread overview]
Message-ID: <BANLkTinz2_RrLiTadGUT41frXxuEsbESqA@mail.gmail.com> (raw)
In-Reply-To: <4DA55ABC.1040505@redhat.com>
On Wed, Apr 13, 2011 at 10:11 AM, Andrew Haley <aph@redhat.com> wrote:
> Before you go any further, it's worth remembering that you're using an
> old version of the GC. I've been told that "Of course, [the new gc]
> will require modification of boehm.cc in GCJ" but not why.
Yes, that is true, but most production systems run even older
versions, and I want a patch that works on those versions. I am now
building packages for Debian lenny (gcc 4.3.2) and Redhat 5 (even
older). I see this patch as a work around that gives me time for the
next step.
> It looks like you're making progress, but I urge you to move to the
> new gc or your time may be wasted on the old one.
The next step is to upgrade to that latest GCC and the latest GC and
the latest Lucene and have that running on Debian Testing.
I will be looking into getting USE_MMAP to work, as I think that would
be a more definite solution. However if I enable it, it segvs.
Are there any specific obstacles for USE_MUNMAP when used in GCJ, or
should it just work?
Erik
next prev parent reply other threads:[~2011-04-14 8:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 8:39 Erik Groeneveld
2011-04-01 8:45 ` Andrew Haley
2011-04-01 9:03 ` Erik Groeneveld
2011-04-01 9:34 ` Andrew Haley
2011-04-02 0:27 ` Boehm, Hans
2011-04-02 9:39 ` Erik Groeneveld
2011-04-03 17:15 ` Erik Groeneveld
2011-04-03 18:00 ` Erik Groeneveld
2011-04-04 8:13 ` Andrew Haley
2011-04-04 8:53 ` Erik Groeneveld
2011-04-04 9:48 ` Andrew Haley
2011-04-05 4:44 ` Boehm, Hans
2011-04-05 8:58 ` Andrew Haley
2011-04-05 6:50 ` Erik Groeneveld
2011-04-05 9:02 ` Andrew Haley
2011-04-05 12:02 ` Erik Groeneveld
2011-04-05 12:55 ` Andrew Haley
2011-04-06 14:30 ` Erik Groeneveld
2011-04-06 18:33 ` Andrew Haley
2011-04-06 18:39 ` David Daney
2011-04-07 17:43 ` Erik Groeneveld
2011-04-08 8:12 ` Erik Groeneveld
2011-04-08 13:56 ` Andrew Haley
2011-04-08 15:35 ` David Daney
2011-04-08 15:53 ` Erik Groeneveld
2011-04-08 15:57 ` Andrew Haley
2011-04-08 15:48 ` Erik Groeneveld
2011-04-09 1:17 ` Boehm, Hans
2011-04-09 8:47 ` Andrew Haley
2011-04-09 10:56 ` Erik Groeneveld
2011-04-10 11:03 ` Erik Groeneveld
2011-04-12 18:43 ` Erik Groeneveld
2011-04-13 8:11 ` Andrew Haley
2011-04-13 12:11 ` Bryce McKinlay
2011-04-13 14:27 ` Andrew Haley
2011-04-14 8:36 ` Erik Groeneveld [this message]
2011-04-14 8:43 ` Andrew Haley
2011-04-14 10:02 ` Erik Groeneveld
2011-04-14 10:50 ` Andrew Haley
2011-04-15 7:32 ` Erik J Groeneveld
2011-04-01 17:41 ` David Daney
2011-04-02 16:21 ` Erik Groeneveld
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=BANLkTinz2_RrLiTadGUT41frXxuEsbESqA@mail.gmail.com \
--to=erik@cq2.nl \
--cc=aph@redhat.com \
--cc=hans.boehm@hp.com \
--cc=java@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).