Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (nike.apache.org: domain of t.p.ellison@gmail.com
 designates 209.85.219.161 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=NGvKpcs37semsr4RUegzdmhqkFMEDXa5QMzLAoSBwFWqtp/G5zsj7dSp6DU2NiXWey
         mEbXRh/K8yG7CJWLlyOxdJdzj5EmXi96n9l8tBLpLU2H1AAzpmI5Yza05AEh0JCZA0oK
         DwFO+WbHwjG53rDS/GXtKOCzD8cuyr4BHM8BQ=
Message-ID: <49CB5BDD.7060801@gmail.com>
Date: Thu, 26 Mar 2009 10:41:33 +0000
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: Re: hymem crash
References: <49C8E9E3.2070608@gmail.com> <49CA0D5F.30906@gmail.com>
 <77577867-2F9F-4CE4-AE8A-7E9CEA6ED163@gmail.com>
 <3b3f27c60903252009g6cb41633l39e92b428a2fc90@mail.gmail.com>
 <49CB5652.1010803@gmail.com>
 <200903261023.n2QANsNH002272@d06av01.portsmouth.uk.ibm.com>
In-Reply-To: <200903261023.n2QANsNH002272@d06av01.portsmouth.uk.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Mark Hindess wrote:
> In message <49CB5652.1010803@gmail.com>, Tim Ellison writes:
>> Nathan Beyer wrote:
>>> Maybe I've just been doing something wrong all along. One way it
>>> works, another it crashes. Here's what I'm doing.
>>>
>>> 1. I have the basic federated build setup.
>>> 2. 'ant rebuild' from top-folder, 'trunk'
>>> 3. 'cd working_classlib\modules\portlib'
>>> 4. 'ant test' - all of the native test pass just fine
>> a good sign
>>
>>> 5. 'cd ..\..\..\' - go back up to top-folder
>>> 6. 'robocopy /mir target\hdk working_classlib\deploy' - copy the
>>> federated build to classlib's deploy folder
>>> 7. 'cd working_classlib'
>>> 8. 'ant test' - after a bit, portlib tests are run and hymem.exe test
>>> blows up in the 'hymem_free_memory' method
>> "blows up" = access violation?  Can you run in windbg and see what is
>> happening?
>>
>> Let me try on my WinXP install and see if the same happens.
> 
> This might be a problem with the hythr from classlib being replaced by
> the hythr from drlvm - IIRC they have different APIs.  Try copying everything
> *except* hythr.dll?

That was my thought too, but then wouldn't you expect much more
catastrophe than a single hymem test failure??

(just rebuilding now)

Regards,
Tim