Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of simon.harmony@gmail.com
 designates 74.125.44.157 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=P3UYUaLx43S+ANoYAo3AqDnrg/+vUi289unxYrvBiOZMiwkf2JDVH7QKO0ZpVMNkGC
         u5QtxnoDrTLbrEC2QlLAqT8Fi0UhyT9rjzuIopFI5CyfxvSe5z5MTze4w6Z8WpJsqXnc
         wyYJG5sHjfGPlOqQ1/oie7oOHsCG2mH6RPsCU=
MIME-Version: 1.0
In-Reply-To: <3db9f87f0905152305p64766516wb733ea79979be4ba@mail.gmail.com>
References: <3db9f87f0905152305p64766516wb733ea79979be4ba@mail.gmail.com>
Date: Sat, 16 May 2009 17:04:50 +0800
Message-ID: <3db9f87f0905160204q2556c2b9m25fbff88d1e76a4d@mail.gmail.com>
Subject: Re: [drlvm][jitrino] write barrier was broken
From: Simon Zhou <simon.harmony@gmail.com>
To: dev@harmony.apache.org
Content-Type: multipart/alternative; boundary=000e0cd6a86a8d9463046a03da09

--000e0cd6a86a8d9463046a03da09
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I think I found the origin of this issue by binary searching the previous
patches, I foud that it is broken since version 747844 (747843 is OK), so
I am guessing the patch of 5826 breaks this.

To replay the error, just add -XX:gc.generate_barrier=true to command line
when running a Java application.
I added some of my guesswork in
https://issues.apache.org/jira/browse/HARMONY-5826

Xiaoming, Would you like to give me advice for this issue? Or is there some
workaroud for it? Thank you very much!

Thanks
Simon

2009/5/16 Simon Zhou <simon.harmony@gmail.com>

> Hi All,
>
>   I am doing my GSoC2009 project of implementing weak reference in
> Concurrent GC. I found that as long as the gc.generate_barrier=true is set,
> VM will crash when it startups (int vm_init2() method). I was following this
> issue these days but did not work out.
>   This issue seem to come out after milestone8, so  I guess it could be
> caused by some patches on Jitrino after M8.
>    Is there anyone else being aware of that? Or could you please provide
> some information about which patch could cause it?
>    Thank you very much!
>
> Thanks
> Simon
>
> --
> From : Simon.Zhou@PPI, Fudan University
>


-- 
>From : Simon.Zhou@PPI, Fudan University

--000e0cd6a86a8d9463046a03da09--