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 gshimansky@gmail.com
 designates 209.85.198.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=GtGjtVtz3Gf+N+wqFJDwue9p5j8MfhHHGI5Boc7hRaByGAm3fMqS+TzK+8k5yL5wM6RzvdcohgScosd1kTS1hv1Yn9v6j+onac8CbbHL2llx4ld6Vyl7Dz4+Une77Fwqd7iT9xRu5BOmeDtWuoveJpfpIaq8OnxmMOJLpylmpco=
Message-ID: <47065850.1050302@gmail.com>
Date: Fri, 05 Oct 2007 19:29:20 +0400
From: Gregory Shimansky <gshimansky@gmail.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: Re: [general] Eclipse Launcher Problem (was Re: [general][M3] release
 r580985 as M3 stable build)
References: <fc2fc95c0710040836p76f46dbhc7b957b20ad5716f@mail.gmail.com>
	 <200710041634.l94GYtBs031640@d12av04.megacenter.de.ibm.com>
 <fc2fc95c0710050202s1ebe7c46i6bd02cdd86b4ff88@mail.gmail.com>
In-Reply-To: <fc2fc95c0710050202s1ebe7c46i6bd02cdd86b4ff88@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sian January wrote:
> I'm happy to try and get some debug output if that would be helpful, or I
> could wait for HARMONY-4006 to be committed and double check that that
> doesn't fix it.

Now that the trunk is unfrozen, I committed HARMONY-4006 patches. So you 
can check whether it is the same bug or something different.

> On 04/10/2007, Mark Hindess <mark.hindess@googlemail.com> wrote:
>>
>> On 4 October 2007 at 16:36, "Sian January" <sianjanuary@googlemail.com>
>> wrote:
>>> Sorry - I think I should have started another thread for this discussion
>> so
>>> we don't clutter up the M3 thread.  Please reply here.
>>>
>>> Thanks,
>>>
>>> Sian
>>>
>>>
>>>
>>> On 04/10/2007, Sian January <sianjanuary@googlemail.com> wrote:
>>>> Thanks Gregory.  So I guess the launcher is using JNI rather than
>> java.exet
>>> o start Eclipse when the jre directory exists.
>>>> By the way, this was also failing for me with the IBM VME.  Does it
>> make
>>>> sense that it would have the same bug?
>> I think there was a bug (crash in the luni JNI on load code, luniglob.c,
>> with portlib == NULL) when using the invocation API but I thought this
>> had been fixed.  Perhaps we only thought about fixing it. (luniglob.c
>> should probably create portlib if it is NULL.)
>>
>> -Mark.
>>
>>
>>
> 
> 


-- 
Gregory