You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Sian January <si...@googlemail.com> on 2007/10/04 17:36:13 UTC
[general] Eclipse Launcher Problem (was Re: [general][M3] release r580985 as M3 stable build)
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 <si...@googlemail.com> wrote:
>
> Thanks Gregory. So I guess the launcher is using JNI rather than java.exeto 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?
>
>
> On 04/10/2007, Gregory Shimansky <gs...@gmail.com> wrote:
> >
> > Sian January wrote:
> > > On 04/10/2007, Tim Ellison <t.p.ellison@gmail.com > wrote:
> > >> Stepan Mishura wrote:
> > >>> Let's make a decision about the last milestone candidate r580985.
> > >>> Shortly, as I can see there is only one issue that blocks its
> > release
> > >>> - HARMONY-4873
> > >>>
> > >>> I'd suggest the next - we wait for objections to postpone the issue
> > >>> resolution to M4 for 72 hours (starting from now) to let everyone to
> > >>> speak up.
> > >>> If there are no objections - we make the release. Also I think we
> > >>> shouldn't keep all this time the trunk frozen so I'd suggest if
> > there
> > >>> are no objections during 24 hours we unfroze the trunk. If after
> > that
> > >>> we get a vote for fixing the issue then a branch is created to make
> > >>> the fix and testing.
> > >> Agreed, although it would be good to hear that the Eclipse 3.3launching
> > >> problem is fixed that Sian posted about on the thread "Re: [eclipse]
> > >> Eclipse 3.3 can not download updates".
> > >
> > >
> > > I've just done some more digging on this and it's only failing when
> > you copy
> > > the Harmony JRE to the eclipse/jre directory (which is new in Eclipse
> > 3.3).
> > > You can still add jre\bin to the path and run eclipse.exe like you did
> > > before. So as it's not a regression and it could take a while to
> > figure out
> > > I would probably say it's not a blocking issue for M3.
> > >
> > > Next question is whether to raise a Harmony bug or an Eclipse bug...
> >
> > There is already a bug about eclipse.exe not being able to launch
> > Harmony when DRLVM is used. It is HARMONY-4006. All patches there are
> > ready to committed after code freeze.
> >
> > BTW it is a windows only bug because of windows specific name
> > decorations for JNI_CreateJavaVM function. On Linux eclipse 3.3 should
> > work without any patches.
> >
> > >> (Sorry that I can't be of much help with fixing things at the moment,
> > >> I'm about to get on an airplane again.)
> > >>
> > >> Regards,
> > >> Tim
> > >>
> > >
> > >
> > >
> >
> >
> > --
> > Gregory
> >
> >
>
>
> --
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
>
--
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: [general] Eclipse Launcher Problem (was Re: [general][M3] release r580985 as M3 stable build)
Posted by Sian January <si...@googlemail.com>.
Hello,
Sorry it's taken me a while to get back to this, but this is still failing
for me with HARMONY-4006 committed so I think it must be a different issue.
I've raised HARMONY-4951 (https://issues.apache.org/jira/browse/HARMONY-4951)
for this issue in case anyone is able to look at it, as I'm not a launcher
or VM expert myself! I'm happy to try and get some more debug information
out though if anyone can direct me on how to do that.
Thanks,
Sian
On 05/10/2007, Gregory Shimansky <gs...@gmail.com> wrote:
>
> 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 <ma...@googlemail.com> wrote:
> >>
> >> On 4 October 2007 at 16:36, "Sian January" <si...@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 <si...@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
>
>
--
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: [general] Eclipse Launcher Problem (was Re: [general][M3] release
r580985 as M3 stable build)
Posted by Gregory Shimansky <gs...@gmail.com>.
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 <ma...@googlemail.com> wrote:
>>
>> On 4 October 2007 at 16:36, "Sian January" <si...@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 <si...@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
Re: [general] Eclipse Launcher Problem (was Re: [general][M3] release r580985 as M3 stable build)
Posted by Sian January <si...@googlemail.com>.
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.
On 04/10/2007, Mark Hindess <ma...@googlemail.com> wrote:
>
>
> On 4 October 2007 at 16:36, "Sian January" <si...@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 <si...@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.
>
>
>
--
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: [general] Eclipse Launcher Problem (was Re: [general][M3] release r580985 as M3 stable build)
Posted by Mark Hindess <ma...@googlemail.com>.
On 4 October 2007 at 16:36, "Sian January" <si...@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 <si...@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.
Re: [general] Eclipse Launcher Problem (was Re: [general][M3] release
r580985 as M3 stable build)
Posted by Gregory Shimansky <gs...@gmail.com>.
Sian January 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.
Sorry, I read your email in M3 thread first and replied to it. Reply
goes below.
> On 04/10/2007, Sian January <si...@googlemail.com> wrote:
>> Thanks Gregory. So I guess the launcher is using JNI rather than java.exeto 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?
Hmm no. In this case it should be a different bug since IBM VME exports
JNI_CreateJavaVM as "JNI_CreateJavaVM" (as sun does), not as
"_JNI_CreateJavaVM@12" as DRLVM currently does. So it is something
different. Maybe eclipse.exe actually uses java.exe when it finds
eclipse/jre directory?...
>> On 04/10/2007, Gregory Shimansky <gs...@gmail.com> wrote:
>>> Sian January wrote:
>>>> On 04/10/2007, Tim Ellison <t.p.ellison@gmail.com > wrote:
>>>>> Stepan Mishura wrote:
>>>>>> Let's make a decision about the last milestone candidate r580985.
>>>>>> Shortly, as I can see there is only one issue that blocks its
>>> release
>>>>>> - HARMONY-4873
>>>>>>
>>>>>> I'd suggest the next - we wait for objections to postpone the issue
>>>>>> resolution to M4 for 72 hours (starting from now) to let everyone to
>>>>>> speak up.
>>>>>> If there are no objections - we make the release. Also I think we
>>>>>> shouldn't keep all this time the trunk frozen so I'd suggest if
>>> there
>>>>>> are no objections during 24 hours we unfroze the trunk. If after
>>> that
>>>>>> we get a vote for fixing the issue then a branch is created to make
>>>>>> the fix and testing.
>>>>> Agreed, although it would be good to hear that the Eclipse 3.3launching
>>>>> problem is fixed that Sian posted about on the thread "Re: [eclipse]
>>>>> Eclipse 3.3 can not download updates".
>>>>
>>>> I've just done some more digging on this and it's only failing when
>>> you copy
>>>> the Harmony JRE to the eclipse/jre directory (which is new in Eclipse
>>> 3.3).
>>>> You can still add jre\bin to the path and run eclipse.exe like you did
>>>> before. So as it's not a regression and it could take a while to
>>> figure out
>>>> I would probably say it's not a blocking issue for M3.
>>>>
>>>> Next question is whether to raise a Harmony bug or an Eclipse bug...
>>> There is already a bug about eclipse.exe not being able to launch
>>> Harmony when DRLVM is used. It is HARMONY-4006. All patches there are
>>> ready to committed after code freeze.
>>>
>>> BTW it is a windows only bug because of windows specific name
>>> decorations for JNI_CreateJavaVM function. On Linux eclipse 3.3 should
>>> work without any patches.
>>>
>>>>> (Sorry that I can't be of much help with fixing things at the moment,
>>>>> I'm about to get on an airplane again.)
>>>>>
>>>>> Regards,
>>>>> Tim
>>>>>
>>>>
>>>>
>>>
>>> --
>>> Gregory
>>>
>>>
>>
>> --
>> Unless stated otherwise above:
>> IBM United Kingdom Limited - Registered in England and Wales with number
>> 741598.
>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>>
>>
>
>
>
--
Gregory