You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Alexey Petrenko <al...@gmail.com> on 2007/09/04 13:18:00 UTC
[eclipse] Eclipse 3.3 crashes on current Harmony
Guys,
I've tried to run In Harmony with Eclipse bundle on the recent
harmony/drlvm build but it crashes silently in the very begining.
I would say that this is very serious regression for us.
I'll continue investigation but it would be nice if someone will try
to investigate it in the same time.
Thanks in advance.
SY, Alexey
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Alexei Fedotov <al...@gmail.com>.
Alexey,
AFAIK, the last switch to the new verifier happened on Aug, 8, see
[1]. I will check if the problem happens from the very beginning or
not.
[1] http://svn.apache.org/viewvc?view=rev&rev=563766
On 9/6/07, Alexey Petrenko <al...@gmail.com> wrote:
> So the new verifier has this issue from the very begining? And this is
> not a regression, right?
>
> Does anybody know when new verifier was commited?
>
> SY, Alexey
>
> 2007/9/6, Alexei Fedotov <al...@gmail.com>:
> > Alexey,
> >
> > Sorry. At the time I wrote that observation I was confused with the
> > alternative verifier convention to return _FALSE to indicate a
> > successful check in checkAccess* functions.
> >
> > The problem happens in a different place and is related to mixing of
> > classes from different class loaders. The fact is that compared class
> > handles reference different class loaders, and this might be problem
> > of the verifier internal cache.
> >
> > I've updated HARMONY-4738 [1] with the latest information, but
> > resolution is not clear yet.
> >
> > Thanks.
> >
> > [1] http://issues.apache.org/jira/browse/HARMONY-4738
> >
> >
> > On 9/6/07, Alexey Petrenko <al...@gmail.com> wrote:
> > > Thanks, Alexei.
> > >
> > > So I would say that we should revert this patch and then think on how
> > > to resolve the issue in better way?
> > >
> > > Thoughts?
> > >
> > > SY, Alexey
> > >
> > > 2007/9/5, Alexei Fedotov <al...@gmail.com>:
> > > > Gregory,
> > > > Thanks for your help!
> > > >
> > > > My observation is that the problem showed itself after the following fix
> > > > http://svn.apache.org/viewvc?view=rev&revision=563763
> > > >
> > > > Tracking things in a debugger I can see that the following new line of
> > > > code returns unexpected result. I will dig further into the behavior
> > > > of this function.
> > > > - return _TRUE;
> > > > + return !class_is_same_package(k_class, referred) &&
> > > > vf_is_extending(k_class, referred);
> > > >
> > > > With best regards, Alexei
> > > >
> > > > On 9/5/07, Mark Hindess <ma...@googlemail.com> wrote:
> > > > >
> > > > > On 5 September 2007 at 16:05, Gregory Shimansky <gs...@gmail.com> wrote:
> > > > > > Alexey Petrenko wrote:
> > > > > > > 2007/9/4, Gregory Shimansky <gs...@gmail.com>:
> > > > > > >> Gregory Shimansky wrote:
> > > > > > >>> It seems to be a bug in verifier, but there weren't any changes in
> > > > > > >>> verifier recently, so I am not sure it is a regression. Probably this
> > > > > > >>> bug was hidden and didn't show up until recently.
> > > > > > >> BTW, building DRLVM with -Duse_original_verifier=true allows eclipse 3.3
> > > > > > >> to start. I think that maybe switching back to older verifier again
> > > > > > >> might improve the situation.
> > > > > > > Yes, this helps. -noverify should also help in this case.
> > > > > > >
> > > > > > > I've created HARMONY-4738 to track the issue.
> > > > > > > It would be nice if someone familiar with the verifier could fix the issue.
> > > > > >
> > > > > > BTW I think I've found out the reason for this bug. Eclipse 3.3 has an
> > > > > > ICU4J implementation bundled with it. It uses ICU 3.6.1 while we have
> > > > > > ICU4J 3.4.4 in bootclasspath.
> > > > > >
> > > > > > In this case ICU classes are loaded from our 3.4.4 JAR file except for
> > > > > > some classes that may not be present in the older version. In this case
> > > > > > they are taken from Eclipse's JAR file which leads to inconsistencies.
> > > > > >
> > > > > > I wonder why older verifier implementation works ok...
> > > > >
> > > > > No idea. I also wonder why J9 is unaffected.
> > > > >
> > > > > FYI: I see similar but not identical problems on Linux.
> > > > >
> > > > > -Mark.
> > > > >
> > > > > > > https://issues.apache.org/jira/browse/HARMONY-4738
> > > > > > >
> > > > > > >>>> 2007/9/4, Alexey Petrenko <al...@gmail.com>:
> > > > > > >>>>> Yes, looks like we really have a regression.
> > > > > > >>>>> I've tried Eclipse with M2 and recent classlib with j9 and works in
> > > > > > >>>>> both cases. But silently crashes silently in the very beging. Even
> > > > > > >>>>> without trace in configuration directory.
> > > > > > >>>>>
> > > > > > >>>>> So we need to investigate the issue.
> > > > > > >>>>>
> > > > > > >>>>> Any help is welcome :)
> > > > > > >>>>>
> > > > > > >>>>> SY, Alexey
> > > > > > >>>>>
> > > > > > >>>>> 2007/9/4, Tim Ellison <t....@gmail.com>:
> > > > > > >>>>>> Leo Li wrote:
> > > > > > >>>>>>> On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
> > > > > > >>>>>>>> Guys,
> > > > > > >>>>>>>>
> > > > > > >>>>>>>> I've tried to run In Harmony with Eclipse bundle on the recent
> > > > > > >>>>>>>> harmony/drlvm build but it crashes silently in the very begining.
> > > > > > >>>>>>>> I would say that this is very serious regression for us.
> > > > > > >>>>>>>>
> > > > > > >>>>>>>> I'll continue investigation but it would be nice if someone will try
> > > > > > >>>>>>>> to investigate it in the same time.
> > > > > > >>>>>>>>
> > > > > > >>>>>>>> Thanks in advance.
> > > > > > >>>>>>>>
> > > > > > >>>>>>>> SY, Alexey
> > > > > > >>>>>>>>
> > > > > > >>>>>>> Yes, it is a serious regression. And do you know when it start to
> > > > > > >>>>>>> fail?
> > > > > > >>>>>>> I will try it when I go to office tomorrow since I have no classlib
> > > > > > >>>>>>> on hand. Not sure whether I can help.:)
> > > > > > >>>>>> FYI: It's working ok for me on the current HEAD of classlib (r572680)
> > > > > > >>>>>> with the IBM VME.
> > > > > > >>>>>>
> > > > > > >>>>>> Regards,
> > > > > > >>>>>> Tim
> > > > > > >>>>>>
> > > > > > >>>
> > > > > > >>
> > > > > > >> --
> > > > > > >> Gregory
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Gregory
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > With best regards,
> > > > Alexei,
> > > > ESSD, Intel
> > > >
> > >
> >
> >
> > --
> > With best regards,
> > Alexei,
> > ESSD, Intel
> >
>
--
With best regards,
Alexei,
ESSD, Intel
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Alexey Petrenko <al...@gmail.com>.
Yes, it works fine now.
SY, Alexey
2007/9/12, Mikhail Loenko <ml...@gmail.com>:
> Hi
>
> Sorry for my silence, I was out for a while.
>
> Has this been resolved? The functionality Alexei was talking
> about is similar in two verifiers and Alexei's change actually rolls back
> some of my August changes (which fixed a bug), so if regression
> tests run smoothly, it's probably OK
>
> Thanks,
> Mikhail
>
> 2007/9/6, Stepan Mishura <st...@gmail.com>:
> > On 9/6/07, Alexey Petrenko <al...@gmail.com> wrote:
> > > So the new verifier has this issue from the very begining? And this is
> > > not a regression, right?
> > >
> > > Does anybody know when new verifier was commited?
> > >
> >
> > $ svn log build/make/components/vm/vmcore.xml
> >
> > <SNIP>
> >
> > ------------------------------------------------------------------------
> > r563766 | mloenko | 2007-08-08 13:24:26 +0700 (Wed, 08 Aug 2007) | 1 line
> >
> > switching default verifier to 3363
> > ------------------------------------------------------------------------
> > r563025 | mloenko | 2007-08-06 11:55:57 +0700 (Mon, 06 Aug 2007) | 1 line
> >
> > switching the verifiers back until newly found issues are resolved
> >
> > <SNIP>
> >
> > ------------------------------------------------------------------------
> > r556809 | mloenko | 2007-07-17 11:36:45 +0700 (Tue, 17 Jul 2007) | 1 line
> >
> > switching default verifier to HARMONY-3363
> >
> > <SNIP>
> >
> > ------------------------------------------------------------------------
> > r556523 | mloenko | 2007-07-16 13:44:55 +0700 (Mon, 16 Jul 2007) | 1 line
> >
> > integration of HARMONY-3363 (contribution of alternative bytecode
> > verifier). Default behavior not switched yet
> >
> > -Stepan.
> >
>
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Mikhail Loenko <ml...@gmail.com>.
Hi
Sorry for my silence, I was out for a while.
Has this been resolved? The functionality Alexei was talking
about is similar in two verifiers and Alexei's change actually rolls back
some of my August changes (which fixed a bug), so if regression
tests run smoothly, it's probably OK
Thanks,
Mikhail
2007/9/6, Stepan Mishura <st...@gmail.com>:
> On 9/6/07, Alexey Petrenko <al...@gmail.com> wrote:
> > So the new verifier has this issue from the very begining? And this is
> > not a regression, right?
> >
> > Does anybody know when new verifier was commited?
> >
>
> $ svn log build/make/components/vm/vmcore.xml
>
> <SNIP>
>
> ------------------------------------------------------------------------
> r563766 | mloenko | 2007-08-08 13:24:26 +0700 (Wed, 08 Aug 2007) | 1 line
>
> switching default verifier to 3363
> ------------------------------------------------------------------------
> r563025 | mloenko | 2007-08-06 11:55:57 +0700 (Mon, 06 Aug 2007) | 1 line
>
> switching the verifiers back until newly found issues are resolved
>
> <SNIP>
>
> ------------------------------------------------------------------------
> r556809 | mloenko | 2007-07-17 11:36:45 +0700 (Tue, 17 Jul 2007) | 1 line
>
> switching default verifier to HARMONY-3363
>
> <SNIP>
>
> ------------------------------------------------------------------------
> r556523 | mloenko | 2007-07-16 13:44:55 +0700 (Mon, 16 Jul 2007) | 1 line
>
> integration of HARMONY-3363 (contribution of alternative bytecode
> verifier). Default behavior not switched yet
>
> -Stepan.
>
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Stepan Mishura <st...@gmail.com>.
On 9/6/07, Alexey Petrenko <al...@gmail.com> wrote:
> So the new verifier has this issue from the very begining? And this is
> not a regression, right?
>
> Does anybody know when new verifier was commited?
>
$ svn log build/make/components/vm/vmcore.xml
<SNIP>
------------------------------------------------------------------------
r563766 | mloenko | 2007-08-08 13:24:26 +0700 (Wed, 08 Aug 2007) | 1 line
switching default verifier to 3363
------------------------------------------------------------------------
r563025 | mloenko | 2007-08-06 11:55:57 +0700 (Mon, 06 Aug 2007) | 1 line
switching the verifiers back until newly found issues are resolved
<SNIP>
------------------------------------------------------------------------
r556809 | mloenko | 2007-07-17 11:36:45 +0700 (Tue, 17 Jul 2007) | 1 line
switching default verifier to HARMONY-3363
<SNIP>
------------------------------------------------------------------------
r556523 | mloenko | 2007-07-16 13:44:55 +0700 (Mon, 16 Jul 2007) | 1 line
integration of HARMONY-3363 (contribution of alternative bytecode
verifier). Default behavior not switched yet
-Stepan.
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Alexey Petrenko <al...@gmail.com>.
So the new verifier has this issue from the very begining? And this is
not a regression, right?
Does anybody know when new verifier was commited?
SY, Alexey
2007/9/6, Alexei Fedotov <al...@gmail.com>:
> Alexey,
>
> Sorry. At the time I wrote that observation I was confused with the
> alternative verifier convention to return _FALSE to indicate a
> successful check in checkAccess* functions.
>
> The problem happens in a different place and is related to mixing of
> classes from different class loaders. The fact is that compared class
> handles reference different class loaders, and this might be problem
> of the verifier internal cache.
>
> I've updated HARMONY-4738 [1] with the latest information, but
> resolution is not clear yet.
>
> Thanks.
>
> [1] http://issues.apache.org/jira/browse/HARMONY-4738
>
>
> On 9/6/07, Alexey Petrenko <al...@gmail.com> wrote:
> > Thanks, Alexei.
> >
> > So I would say that we should revert this patch and then think on how
> > to resolve the issue in better way?
> >
> > Thoughts?
> >
> > SY, Alexey
> >
> > 2007/9/5, Alexei Fedotov <al...@gmail.com>:
> > > Gregory,
> > > Thanks for your help!
> > >
> > > My observation is that the problem showed itself after the following fix
> > > http://svn.apache.org/viewvc?view=rev&revision=563763
> > >
> > > Tracking things in a debugger I can see that the following new line of
> > > code returns unexpected result. I will dig further into the behavior
> > > of this function.
> > > - return _TRUE;
> > > + return !class_is_same_package(k_class, referred) &&
> > > vf_is_extending(k_class, referred);
> > >
> > > With best regards, Alexei
> > >
> > > On 9/5/07, Mark Hindess <ma...@googlemail.com> wrote:
> > > >
> > > > On 5 September 2007 at 16:05, Gregory Shimansky <gs...@gmail.com> wrote:
> > > > > Alexey Petrenko wrote:
> > > > > > 2007/9/4, Gregory Shimansky <gs...@gmail.com>:
> > > > > >> Gregory Shimansky wrote:
> > > > > >>> It seems to be a bug in verifier, but there weren't any changes in
> > > > > >>> verifier recently, so I am not sure it is a regression. Probably this
> > > > > >>> bug was hidden and didn't show up until recently.
> > > > > >> BTW, building DRLVM with -Duse_original_verifier=true allows eclipse 3.3
> > > > > >> to start. I think that maybe switching back to older verifier again
> > > > > >> might improve the situation.
> > > > > > Yes, this helps. -noverify should also help in this case.
> > > > > >
> > > > > > I've created HARMONY-4738 to track the issue.
> > > > > > It would be nice if someone familiar with the verifier could fix the issue.
> > > > >
> > > > > BTW I think I've found out the reason for this bug. Eclipse 3.3 has an
> > > > > ICU4J implementation bundled with it. It uses ICU 3.6.1 while we have
> > > > > ICU4J 3.4.4 in bootclasspath.
> > > > >
> > > > > In this case ICU classes are loaded from our 3.4.4 JAR file except for
> > > > > some classes that may not be present in the older version. In this case
> > > > > they are taken from Eclipse's JAR file which leads to inconsistencies.
> > > > >
> > > > > I wonder why older verifier implementation works ok...
> > > >
> > > > No idea. I also wonder why J9 is unaffected.
> > > >
> > > > FYI: I see similar but not identical problems on Linux.
> > > >
> > > > -Mark.
> > > >
> > > > > > https://issues.apache.org/jira/browse/HARMONY-4738
> > > > > >
> > > > > >>>> 2007/9/4, Alexey Petrenko <al...@gmail.com>:
> > > > > >>>>> Yes, looks like we really have a regression.
> > > > > >>>>> I've tried Eclipse with M2 and recent classlib with j9 and works in
> > > > > >>>>> both cases. But silently crashes silently in the very beging. Even
> > > > > >>>>> without trace in configuration directory.
> > > > > >>>>>
> > > > > >>>>> So we need to investigate the issue.
> > > > > >>>>>
> > > > > >>>>> Any help is welcome :)
> > > > > >>>>>
> > > > > >>>>> SY, Alexey
> > > > > >>>>>
> > > > > >>>>> 2007/9/4, Tim Ellison <t....@gmail.com>:
> > > > > >>>>>> Leo Li wrote:
> > > > > >>>>>>> On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
> > > > > >>>>>>>> Guys,
> > > > > >>>>>>>>
> > > > > >>>>>>>> I've tried to run In Harmony with Eclipse bundle on the recent
> > > > > >>>>>>>> harmony/drlvm build but it crashes silently in the very begining.
> > > > > >>>>>>>> I would say that this is very serious regression for us.
> > > > > >>>>>>>>
> > > > > >>>>>>>> I'll continue investigation but it would be nice if someone will try
> > > > > >>>>>>>> to investigate it in the same time.
> > > > > >>>>>>>>
> > > > > >>>>>>>> Thanks in advance.
> > > > > >>>>>>>>
> > > > > >>>>>>>> SY, Alexey
> > > > > >>>>>>>>
> > > > > >>>>>>> Yes, it is a serious regression. And do you know when it start to
> > > > > >>>>>>> fail?
> > > > > >>>>>>> I will try it when I go to office tomorrow since I have no classlib
> > > > > >>>>>>> on hand. Not sure whether I can help.:)
> > > > > >>>>>> FYI: It's working ok for me on the current HEAD of classlib (r572680)
> > > > > >>>>>> with the IBM VME.
> > > > > >>>>>>
> > > > > >>>>>> Regards,
> > > > > >>>>>> Tim
> > > > > >>>>>>
> > > > > >>>
> > > > > >>
> > > > > >> --
> > > > > >> Gregory
> > > > > >>
> > > > > >>
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Gregory
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > With best regards,
> > > Alexei,
> > > ESSD, Intel
> > >
> >
>
>
> --
> With best regards,
> Alexei,
> ESSD, Intel
>
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Alexei Fedotov <al...@gmail.com>.
Alexey,
Sorry. At the time I wrote that observation I was confused with the
alternative verifier convention to return _FALSE to indicate a
successful check in checkAccess* functions.
The problem happens in a different place and is related to mixing of
classes from different class loaders. The fact is that compared class
handles reference different class loaders, and this might be problem
of the verifier internal cache.
I've updated HARMONY-4738 [1] with the latest information, but
resolution is not clear yet.
Thanks.
[1] http://issues.apache.org/jira/browse/HARMONY-4738
On 9/6/07, Alexey Petrenko <al...@gmail.com> wrote:
> Thanks, Alexei.
>
> So I would say that we should revert this patch and then think on how
> to resolve the issue in better way?
>
> Thoughts?
>
> SY, Alexey
>
> 2007/9/5, Alexei Fedotov <al...@gmail.com>:
> > Gregory,
> > Thanks for your help!
> >
> > My observation is that the problem showed itself after the following fix
> > http://svn.apache.org/viewvc?view=rev&revision=563763
> >
> > Tracking things in a debugger I can see that the following new line of
> > code returns unexpected result. I will dig further into the behavior
> > of this function.
> > - return _TRUE;
> > + return !class_is_same_package(k_class, referred) &&
> > vf_is_extending(k_class, referred);
> >
> > With best regards, Alexei
> >
> > On 9/5/07, Mark Hindess <ma...@googlemail.com> wrote:
> > >
> > > On 5 September 2007 at 16:05, Gregory Shimansky <gs...@gmail.com> wrote:
> > > > Alexey Petrenko wrote:
> > > > > 2007/9/4, Gregory Shimansky <gs...@gmail.com>:
> > > > >> Gregory Shimansky wrote:
> > > > >>> It seems to be a bug in verifier, but there weren't any changes in
> > > > >>> verifier recently, so I am not sure it is a regression. Probably this
> > > > >>> bug was hidden and didn't show up until recently.
> > > > >> BTW, building DRLVM with -Duse_original_verifier=true allows eclipse 3.3
> > > > >> to start. I think that maybe switching back to older verifier again
> > > > >> might improve the situation.
> > > > > Yes, this helps. -noverify should also help in this case.
> > > > >
> > > > > I've created HARMONY-4738 to track the issue.
> > > > > It would be nice if someone familiar with the verifier could fix the issue.
> > > >
> > > > BTW I think I've found out the reason for this bug. Eclipse 3.3 has an
> > > > ICU4J implementation bundled with it. It uses ICU 3.6.1 while we have
> > > > ICU4J 3.4.4 in bootclasspath.
> > > >
> > > > In this case ICU classes are loaded from our 3.4.4 JAR file except for
> > > > some classes that may not be present in the older version. In this case
> > > > they are taken from Eclipse's JAR file which leads to inconsistencies.
> > > >
> > > > I wonder why older verifier implementation works ok...
> > >
> > > No idea. I also wonder why J9 is unaffected.
> > >
> > > FYI: I see similar but not identical problems on Linux.
> > >
> > > -Mark.
> > >
> > > > > https://issues.apache.org/jira/browse/HARMONY-4738
> > > > >
> > > > >>>> 2007/9/4, Alexey Petrenko <al...@gmail.com>:
> > > > >>>>> Yes, looks like we really have a regression.
> > > > >>>>> I've tried Eclipse with M2 and recent classlib with j9 and works in
> > > > >>>>> both cases. But silently crashes silently in the very beging. Even
> > > > >>>>> without trace in configuration directory.
> > > > >>>>>
> > > > >>>>> So we need to investigate the issue.
> > > > >>>>>
> > > > >>>>> Any help is welcome :)
> > > > >>>>>
> > > > >>>>> SY, Alexey
> > > > >>>>>
> > > > >>>>> 2007/9/4, Tim Ellison <t....@gmail.com>:
> > > > >>>>>> Leo Li wrote:
> > > > >>>>>>> On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
> > > > >>>>>>>> Guys,
> > > > >>>>>>>>
> > > > >>>>>>>> I've tried to run In Harmony with Eclipse bundle on the recent
> > > > >>>>>>>> harmony/drlvm build but it crashes silently in the very begining.
> > > > >>>>>>>> I would say that this is very serious regression for us.
> > > > >>>>>>>>
> > > > >>>>>>>> I'll continue investigation but it would be nice if someone will try
> > > > >>>>>>>> to investigate it in the same time.
> > > > >>>>>>>>
> > > > >>>>>>>> Thanks in advance.
> > > > >>>>>>>>
> > > > >>>>>>>> SY, Alexey
> > > > >>>>>>>>
> > > > >>>>>>> Yes, it is a serious regression. And do you know when it start to
> > > > >>>>>>> fail?
> > > > >>>>>>> I will try it when I go to office tomorrow since I have no classlib
> > > > >>>>>>> on hand. Not sure whether I can help.:)
> > > > >>>>>> FYI: It's working ok for me on the current HEAD of classlib (r572680)
> > > > >>>>>> with the IBM VME.
> > > > >>>>>>
> > > > >>>>>> Regards,
> > > > >>>>>> Tim
> > > > >>>>>>
> > > > >>>
> > > > >>
> > > > >> --
> > > > >> Gregory
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > > > --
> > > > Gregory
> > > >
> > >
> > >
> > >
> >
> >
> > --
> > With best regards,
> > Alexei,
> > ESSD, Intel
> >
>
--
With best regards,
Alexei,
ESSD, Intel
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Alexey Petrenko <al...@gmail.com>.
Thanks, Alexei.
So I would say that we should revert this patch and then think on how
to resolve the issue in better way?
Thoughts?
SY, Alexey
2007/9/5, Alexei Fedotov <al...@gmail.com>:
> Gregory,
> Thanks for your help!
>
> My observation is that the problem showed itself after the following fix
> http://svn.apache.org/viewvc?view=rev&revision=563763
>
> Tracking things in a debugger I can see that the following new line of
> code returns unexpected result. I will dig further into the behavior
> of this function.
> - return _TRUE;
> + return !class_is_same_package(k_class, referred) &&
> vf_is_extending(k_class, referred);
>
> With best regards, Alexei
>
> On 9/5/07, Mark Hindess <ma...@googlemail.com> wrote:
> >
> > On 5 September 2007 at 16:05, Gregory Shimansky <gs...@gmail.com> wrote:
> > > Alexey Petrenko wrote:
> > > > 2007/9/4, Gregory Shimansky <gs...@gmail.com>:
> > > >> Gregory Shimansky wrote:
> > > >>> It seems to be a bug in verifier, but there weren't any changes in
> > > >>> verifier recently, so I am not sure it is a regression. Probably this
> > > >>> bug was hidden and didn't show up until recently.
> > > >> BTW, building DRLVM with -Duse_original_verifier=true allows eclipse 3.3
> > > >> to start. I think that maybe switching back to older verifier again
> > > >> might improve the situation.
> > > > Yes, this helps. -noverify should also help in this case.
> > > >
> > > > I've created HARMONY-4738 to track the issue.
> > > > It would be nice if someone familiar with the verifier could fix the issue.
> > >
> > > BTW I think I've found out the reason for this bug. Eclipse 3.3 has an
> > > ICU4J implementation bundled with it. It uses ICU 3.6.1 while we have
> > > ICU4J 3.4.4 in bootclasspath.
> > >
> > > In this case ICU classes are loaded from our 3.4.4 JAR file except for
> > > some classes that may not be present in the older version. In this case
> > > they are taken from Eclipse's JAR file which leads to inconsistencies.
> > >
> > > I wonder why older verifier implementation works ok...
> >
> > No idea. I also wonder why J9 is unaffected.
> >
> > FYI: I see similar but not identical problems on Linux.
> >
> > -Mark.
> >
> > > > https://issues.apache.org/jira/browse/HARMONY-4738
> > > >
> > > >>>> 2007/9/4, Alexey Petrenko <al...@gmail.com>:
> > > >>>>> Yes, looks like we really have a regression.
> > > >>>>> I've tried Eclipse with M2 and recent classlib with j9 and works in
> > > >>>>> both cases. But silently crashes silently in the very beging. Even
> > > >>>>> without trace in configuration directory.
> > > >>>>>
> > > >>>>> So we need to investigate the issue.
> > > >>>>>
> > > >>>>> Any help is welcome :)
> > > >>>>>
> > > >>>>> SY, Alexey
> > > >>>>>
> > > >>>>> 2007/9/4, Tim Ellison <t....@gmail.com>:
> > > >>>>>> Leo Li wrote:
> > > >>>>>>> On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
> > > >>>>>>>> Guys,
> > > >>>>>>>>
> > > >>>>>>>> I've tried to run In Harmony with Eclipse bundle on the recent
> > > >>>>>>>> harmony/drlvm build but it crashes silently in the very begining.
> > > >>>>>>>> I would say that this is very serious regression for us.
> > > >>>>>>>>
> > > >>>>>>>> I'll continue investigation but it would be nice if someone will try
> > > >>>>>>>> to investigate it in the same time.
> > > >>>>>>>>
> > > >>>>>>>> Thanks in advance.
> > > >>>>>>>>
> > > >>>>>>>> SY, Alexey
> > > >>>>>>>>
> > > >>>>>>> Yes, it is a serious regression. And do you know when it start to
> > > >>>>>>> fail?
> > > >>>>>>> I will try it when I go to office tomorrow since I have no classlib
> > > >>>>>>> on hand. Not sure whether I can help.:)
> > > >>>>>> FYI: It's working ok for me on the current HEAD of classlib (r572680)
> > > >>>>>> with the IBM VME.
> > > >>>>>>
> > > >>>>>> Regards,
> > > >>>>>> Tim
> > > >>>>>>
> > > >>>
> > > >>
> > > >> --
> > > >> Gregory
> > > >>
> > > >>
> > > >
> > >
> > >
> > > --
> > > Gregory
> > >
> >
> >
> >
>
>
> --
> With best regards,
> Alexei,
> ESSD, Intel
>
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Alexei Fedotov <al...@gmail.com>.
Gregory,
Thanks for your help!
My observation is that the problem showed itself after the following fix
http://svn.apache.org/viewvc?view=rev&revision=563763
Tracking things in a debugger I can see that the following new line of
code returns unexpected result. I will dig further into the behavior
of this function.
- return _TRUE;
+ return !class_is_same_package(k_class, referred) &&
vf_is_extending(k_class, referred);
With best regards, Alexei
On 9/5/07, Mark Hindess <ma...@googlemail.com> wrote:
>
> On 5 September 2007 at 16:05, Gregory Shimansky <gs...@gmail.com> wrote:
> > Alexey Petrenko wrote:
> > > 2007/9/4, Gregory Shimansky <gs...@gmail.com>:
> > >> Gregory Shimansky wrote:
> > >>> It seems to be a bug in verifier, but there weren't any changes in
> > >>> verifier recently, so I am not sure it is a regression. Probably this
> > >>> bug was hidden and didn't show up until recently.
> > >> BTW, building DRLVM with -Duse_original_verifier=true allows eclipse 3.3
> > >> to start. I think that maybe switching back to older verifier again
> > >> might improve the situation.
> > > Yes, this helps. -noverify should also help in this case.
> > >
> > > I've created HARMONY-4738 to track the issue.
> > > It would be nice if someone familiar with the verifier could fix the issue.
> >
> > BTW I think I've found out the reason for this bug. Eclipse 3.3 has an
> > ICU4J implementation bundled with it. It uses ICU 3.6.1 while we have
> > ICU4J 3.4.4 in bootclasspath.
> >
> > In this case ICU classes are loaded from our 3.4.4 JAR file except for
> > some classes that may not be present in the older version. In this case
> > they are taken from Eclipse's JAR file which leads to inconsistencies.
> >
> > I wonder why older verifier implementation works ok...
>
> No idea. I also wonder why J9 is unaffected.
>
> FYI: I see similar but not identical problems on Linux.
>
> -Mark.
>
> > > https://issues.apache.org/jira/browse/HARMONY-4738
> > >
> > >>>> 2007/9/4, Alexey Petrenko <al...@gmail.com>:
> > >>>>> Yes, looks like we really have a regression.
> > >>>>> I've tried Eclipse with M2 and recent classlib with j9 and works in
> > >>>>> both cases. But silently crashes silently in the very beging. Even
> > >>>>> without trace in configuration directory.
> > >>>>>
> > >>>>> So we need to investigate the issue.
> > >>>>>
> > >>>>> Any help is welcome :)
> > >>>>>
> > >>>>> SY, Alexey
> > >>>>>
> > >>>>> 2007/9/4, Tim Ellison <t....@gmail.com>:
> > >>>>>> Leo Li wrote:
> > >>>>>>> On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
> > >>>>>>>> Guys,
> > >>>>>>>>
> > >>>>>>>> I've tried to run In Harmony with Eclipse bundle on the recent
> > >>>>>>>> harmony/drlvm build but it crashes silently in the very begining.
> > >>>>>>>> I would say that this is very serious regression for us.
> > >>>>>>>>
> > >>>>>>>> I'll continue investigation but it would be nice if someone will try
> > >>>>>>>> to investigate it in the same time.
> > >>>>>>>>
> > >>>>>>>> Thanks in advance.
> > >>>>>>>>
> > >>>>>>>> SY, Alexey
> > >>>>>>>>
> > >>>>>>> Yes, it is a serious regression. And do you know when it start to
> > >>>>>>> fail?
> > >>>>>>> I will try it when I go to office tomorrow since I have no classlib
> > >>>>>>> on hand. Not sure whether I can help.:)
> > >>>>>> FYI: It's working ok for me on the current HEAD of classlib (r572680)
> > >>>>>> with the IBM VME.
> > >>>>>>
> > >>>>>> Regards,
> > >>>>>> Tim
> > >>>>>>
> > >>>
> > >>
> > >> --
> > >> Gregory
> > >>
> > >>
> > >
> >
> >
> > --
> > Gregory
> >
>
>
>
--
With best regards,
Alexei,
ESSD, Intel
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Mark Hindess <ma...@googlemail.com>.
On 5 September 2007 at 16:05, Gregory Shimansky <gs...@gmail.com> wrote:
> Alexey Petrenko wrote:
> > 2007/9/4, Gregory Shimansky <gs...@gmail.com>:
> >> Gregory Shimansky wrote:
> >>> It seems to be a bug in verifier, but there weren't any changes in
> >>> verifier recently, so I am not sure it is a regression. Probably this
> >>> bug was hidden and didn't show up until recently.
> >> BTW, building DRLVM with -Duse_original_verifier=true allows eclipse 3.3
> >> to start. I think that maybe switching back to older verifier again
> >> might improve the situation.
> > Yes, this helps. -noverify should also help in this case.
> >
> > I've created HARMONY-4738 to track the issue.
> > It would be nice if someone familiar with the verifier could fix the issue.
>
> BTW I think I've found out the reason for this bug. Eclipse 3.3 has an
> ICU4J implementation bundled with it. It uses ICU 3.6.1 while we have
> ICU4J 3.4.4 in bootclasspath.
>
> In this case ICU classes are loaded from our 3.4.4 JAR file except for
> some classes that may not be present in the older version. In this case
> they are taken from Eclipse's JAR file which leads to inconsistencies.
>
> I wonder why older verifier implementation works ok...
No idea. I also wonder why J9 is unaffected.
FYI: I see similar but not identical problems on Linux.
-Mark.
> > https://issues.apache.org/jira/browse/HARMONY-4738
> >
> >>>> 2007/9/4, Alexey Petrenko <al...@gmail.com>:
> >>>>> Yes, looks like we really have a regression.
> >>>>> I've tried Eclipse with M2 and recent classlib with j9 and works in
> >>>>> both cases. But silently crashes silently in the very beging. Even
> >>>>> without trace in configuration directory.
> >>>>>
> >>>>> So we need to investigate the issue.
> >>>>>
> >>>>> Any help is welcome :)
> >>>>>
> >>>>> SY, Alexey
> >>>>>
> >>>>> 2007/9/4, Tim Ellison <t....@gmail.com>:
> >>>>>> Leo Li wrote:
> >>>>>>> On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
> >>>>>>>> Guys,
> >>>>>>>>
> >>>>>>>> I've tried to run In Harmony with Eclipse bundle on the recent
> >>>>>>>> harmony/drlvm build but it crashes silently in the very begining.
> >>>>>>>> I would say that this is very serious regression for us.
> >>>>>>>>
> >>>>>>>> I'll continue investigation but it would be nice if someone will try
> >>>>>>>> to investigate it in the same time.
> >>>>>>>>
> >>>>>>>> Thanks in advance.
> >>>>>>>>
> >>>>>>>> SY, Alexey
> >>>>>>>>
> >>>>>>> Yes, it is a serious regression. And do you know when it start to
> >>>>>>> fail?
> >>>>>>> I will try it when I go to office tomorrow since I have no classlib
> >>>>>>> on hand. Not sure whether I can help.:)
> >>>>>> FYI: It's working ok for me on the current HEAD of classlib (r572680)
> >>>>>> with the IBM VME.
> >>>>>>
> >>>>>> Regards,
> >>>>>> Tim
> >>>>>>
> >>>
> >>
> >> --
> >> Gregory
> >>
> >>
> >
>
>
> --
> Gregory
>
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Gregory Shimansky <gs...@gmail.com>.
Alexey Petrenko wrote:
> 2007/9/4, Gregory Shimansky <gs...@gmail.com>:
>> Gregory Shimansky wrote:
>>> It seems to be a bug in verifier, but there weren't any changes in
>>> verifier recently, so I am not sure it is a regression. Probably this
>>> bug was hidden and didn't show up until recently.
>> BTW, building DRLVM with -Duse_original_verifier=true allows eclipse 3.3
>> to start. I think that maybe switching back to older verifier again
>> might improve the situation.
> Yes, this helps. -noverify should also help in this case.
>
> I've created HARMONY-4738 to track the issue.
> It would be nice if someone familiar with the verifier could fix the issue.
BTW I think I've found out the reason for this bug. Eclipse 3.3 has an
ICU4J implementation bundled with it. It uses ICU 3.6.1 while we have
ICU4J 3.4.4 in bootclasspath.
In this case ICU classes are loaded from our 3.4.4 JAR file except for
some classes that may not be present in the older version. In this case
they are taken from Eclipse's JAR file which leads to inconsistencies.
I wonder why older verifier implementation works ok...
> https://issues.apache.org/jira/browse/HARMONY-4738
>
>>>> 2007/9/4, Alexey Petrenko <al...@gmail.com>:
>>>>> Yes, looks like we really have a regression.
>>>>> I've tried Eclipse with M2 and recent classlib with j9 and works in
>>>>> both cases. But silently crashes silently in the very beging. Even
>>>>> without trace in configuration directory.
>>>>>
>>>>> So we need to investigate the issue.
>>>>>
>>>>> Any help is welcome :)
>>>>>
>>>>> SY, Alexey
>>>>>
>>>>> 2007/9/4, Tim Ellison <t....@gmail.com>:
>>>>>> Leo Li wrote:
>>>>>>> On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
>>>>>>>> Guys,
>>>>>>>>
>>>>>>>> I've tried to run In Harmony with Eclipse bundle on the recent
>>>>>>>> harmony/drlvm build but it crashes silently in the very begining.
>>>>>>>> I would say that this is very serious regression for us.
>>>>>>>>
>>>>>>>> I'll continue investigation but it would be nice if someone will try
>>>>>>>> to investigate it in the same time.
>>>>>>>>
>>>>>>>> Thanks in advance.
>>>>>>>>
>>>>>>>> SY, Alexey
>>>>>>>>
>>>>>>> Yes, it is a serious regression. And do you know when it start to
>>>>>>> fail?
>>>>>>> I will try it when I go to office tomorrow since I have no classlib
>>>>>>> on hand. Not sure whether I can help.:)
>>>>>> FYI: It's working ok for me on the current HEAD of classlib (r572680)
>>>>>> with the IBM VME.
>>>>>>
>>>>>> Regards,
>>>>>> Tim
>>>>>>
>>>
>>
>> --
>> Gregory
>>
>>
>
--
Gregory
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Alexey Petrenko <al...@gmail.com>.
2007/9/4, Gregory Shimansky <gs...@gmail.com>:
> Gregory Shimansky wrote:
> > It seems to be a bug in verifier, but there weren't any changes in
> > verifier recently, so I am not sure it is a regression. Probably this
> > bug was hidden and didn't show up until recently.
>
> BTW, building DRLVM with -Duse_original_verifier=true allows eclipse 3.3
> to start. I think that maybe switching back to older verifier again
> might improve the situation.
Yes, this helps. -noverify should also help in this case.
I've created HARMONY-4738 to track the issue.
It would be nice if someone familiar with the verifier could fix the issue.
Thanks in advance.
SY, Alexey
https://issues.apache.org/jira/browse/HARMONY-4738
>
> >> 2007/9/4, Alexey Petrenko <al...@gmail.com>:
> >>> Yes, looks like we really have a regression.
> >>> I've tried Eclipse with M2 and recent classlib with j9 and works in
> >>> both cases. But silently crashes silently in the very beging. Even
> >>> without trace in configuration directory.
> >>>
> >>> So we need to investigate the issue.
> >>>
> >>> Any help is welcome :)
> >>>
> >>> SY, Alexey
> >>>
> >>> 2007/9/4, Tim Ellison <t....@gmail.com>:
> >>>> Leo Li wrote:
> >>>>> On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
> >>>>>> Guys,
> >>>>>>
> >>>>>> I've tried to run In Harmony with Eclipse bundle on the recent
> >>>>>> harmony/drlvm build but it crashes silently in the very begining.
> >>>>>> I would say that this is very serious regression for us.
> >>>>>>
> >>>>>> I'll continue investigation but it would be nice if someone will try
> >>>>>> to investigate it in the same time.
> >>>>>>
> >>>>>> Thanks in advance.
> >>>>>>
> >>>>>> SY, Alexey
> >>>>>>
> >>>>> Yes, it is a serious regression. And do you know when it start to
> >>>>> fail?
> >>>>> I will try it when I go to office tomorrow since I have no classlib
> >>>>> on hand. Not sure whether I can help.:)
> >>>> FYI: It's working ok for me on the current HEAD of classlib (r572680)
> >>>> with the IBM VME.
> >>>>
> >>>> Regards,
> >>>> Tim
> >>>>
> >>
> >
> >
>
>
> --
> Gregory
>
>
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Gregory Shimansky <gs...@gmail.com>.
Gregory Shimansky wrote:
> It seems to be a bug in verifier, but there weren't any changes in
> verifier recently, so I am not sure it is a regression. Probably this
> bug was hidden and didn't show up until recently.
BTW, building DRLVM with -Duse_original_verifier=true allows eclipse 3.3
to start. I think that maybe switching back to older verifier again
might improve the situation.
>> 2007/9/4, Alexey Petrenko <al...@gmail.com>:
>>> Yes, looks like we really have a regression.
>>> I've tried Eclipse with M2 and recent classlib with j9 and works in
>>> both cases. But silently crashes silently in the very beging. Even
>>> without trace in configuration directory.
>>>
>>> So we need to investigate the issue.
>>>
>>> Any help is welcome :)
>>>
>>> SY, Alexey
>>>
>>> 2007/9/4, Tim Ellison <t....@gmail.com>:
>>>> Leo Li wrote:
>>>>> On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
>>>>>> Guys,
>>>>>>
>>>>>> I've tried to run In Harmony with Eclipse bundle on the recent
>>>>>> harmony/drlvm build but it crashes silently in the very begining.
>>>>>> I would say that this is very serious regression for us.
>>>>>>
>>>>>> I'll continue investigation but it would be nice if someone will try
>>>>>> to investigate it in the same time.
>>>>>>
>>>>>> Thanks in advance.
>>>>>>
>>>>>> SY, Alexey
>>>>>>
>>>>> Yes, it is a serious regression. And do you know when it start to
>>>>> fail?
>>>>> I will try it when I go to office tomorrow since I have no classlib
>>>>> on hand. Not sure whether I can help.:)
>>>> FYI: It's working ok for me on the current HEAD of classlib (r572680)
>>>> with the IBM VME.
>>>>
>>>> Regards,
>>>> Tim
>>>>
>>
>
>
--
Gregory
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Gregory Shimansky <gs...@gmail.com>.
Alexey Petrenko wrote:
> Forget to say: windowsXP - release build
I took a look and eclipse 3.3, and indeed it fails to start up. The
message on windows could be seen in the terminal if you use eclipsec.exe
(console exe), it prints it to console. The message happens in debug and
release, on linux as well because it is not platform dependent, it is a
VerifyError exception with a very long stack trace:
Uncaught exception in Thread-14:
java.lang.VerifyError:
com/ibm/icu/impl/ICUResourceBundleImpl/getBundle()Lcom/ibm/icu/impl/ICUResourceBundle;,
pass: 2, instr: 32, reason: incompartible argument
at java.lang.ClassLoader.defineClass0(ClassLoader.java)
at java.lang.ClassLoader.defineClass(ClassLoader.java:438)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:161)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:501)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:471)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:430)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:413)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:189)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:340)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:408)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
at java.lang.ClassLoader.loadClass(ClassLoader.java:319)
at
com.ibm.icu.impl.ICUResourceBundle.instantiateBundle(ICUResourceBundle.java:1195)
at
com.ibm.icu.impl.ICUResourceBundle.getBundleInstance(ICUResourceBundle.java:1163)
at
com.ibm.icu.util.UResourceBundle.getRootType(UResourceBundle.java:418)
at
com.ibm.icu.util.UResourceBundle.instantiateBundle(UResourceBundle.java:466)
at
com.ibm.icu.util.UResourceBundle.getBundleInstance(UResourceBundle.java:123)
at
com.ibm.icu.util.UResourceBundle.getBundleInstance(UResourceBundle.java:105)
at
com.ibm.icu.util.UResourceBundle.getBundleInstance(UResourceBundle.java:186)
at
com.ibm.icu.text.RuleBasedCollator.<clinit>(RuleBasedCollator.java:1764)
at
com.ibm.icu.text.CollatorServiceShim$1$CollatorFactory.handleCreate(CollatorServiceShim.java:114)
at
com.ibm.icu.impl.ICULocaleService$LocaleKeyFactory.create(ICULocaleService.java:378)
at com.ibm.icu.impl.ICUService.getKey(ICUService.java:463)
at com.ibm.icu.impl.ICUService.getKey(ICUService.java:383)
at com.ibm.icu.impl.ICULocaleService.get(ICULocaleService.java:72)
at com.ibm.icu.impl.ICULocaleService.get(ICULocaleService.java:56)
at
com.ibm.icu.text.CollatorServiceShim.getInstance(CollatorServiceShim.java:34)
at com.ibm.icu.text.Collator.getInstance(Collator.java:483)
at com.ibm.icu.text.Collator.getInstance(Collator.java:315)
at
org.eclipse.ui.actions.PerspectiveMenu$2.<init>(PerspectiveMenu.java:76)
at
org.eclipse.ui.actions.PerspectiveMenu.<init>(PerspectiveMenu.java:75)
at
org.eclipse.ui.internal.ChangeToPerspectiveMenu.<init>(ChangeToPerspectiveMenu.java:36)
at
org.eclipse.ui.actions.ContributionItemFactory$6.create(ContributionItemFactory.java:189)
at
org.eclipse.ui.internal.ide.WorkbenchActionBuilder.addPerspectiveActions(WorkbenchActionBuilder.java:688)
at
org.eclipse.ui.internal.ide.WorkbenchActionBuilder.createWindowMenu(WorkbenchActionBuilder.java:665)
at
org.eclipse.ui.internal.ide.WorkbenchActionBuilder.fillMenuBar(WorkbenchActionBuilder.java:453)
at
org.eclipse.ui.application.ActionBarAdvisor.fillActionBars(ActionBarAdvisor.java:150)
at
org.eclipse.ui.internal.ide.WorkbenchActionBuilder.fillActionBars(WorkbenchActionBuilder.java:360)
at
org.eclipse.ui.internal.WorkbenchWindow.fillActionBars(WorkbenchWindow.java:3294)
at
org.eclipse.ui.internal.WorkbenchWindow.<init>(WorkbenchWindow.java:380)
at
org.eclipse.ui.internal.Workbench.newWorkbenchWindow(Workbench.java:1725)
at org.eclipse.ui.internal.Workbench.access$14(Workbench.java:1724)
at
org.eclipse.ui.internal.Workbench$18.runWithException(Workbench.java:1001)
at
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
at
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974)
at
org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:797)
at
org.eclipse.ui.internal.Workbench$25.runWithException(Workbench.java:1342)
at
org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
at
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2309)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
at java.lang.reflect.Method.invoke(Method.java:317)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
at java.lang.reflect.Method.invoke(Method.java:317)
at org.apache.harmony.vm.JarRunner.main(JarRunner.java:80)
It seems to be a bug in verifier, but there weren't any changes in
verifier recently, so I am not sure it is a regression. Probably this
bug was hidden and didn't show up until recently.
> 2007/9/4, Alexey Petrenko <al...@gmail.com>:
>> Yes, looks like we really have a regression.
>> I've tried Eclipse with M2 and recent classlib with j9 and works in
>> both cases. But silently crashes silently in the very beging. Even
>> without trace in configuration directory.
>>
>> So we need to investigate the issue.
>>
>> Any help is welcome :)
>>
>> SY, Alexey
>>
>> 2007/9/4, Tim Ellison <t....@gmail.com>:
>>> Leo Li wrote:
>>>> On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
>>>>> Guys,
>>>>>
>>>>> I've tried to run In Harmony with Eclipse bundle on the recent
>>>>> harmony/drlvm build but it crashes silently in the very begining.
>>>>> I would say that this is very serious regression for us.
>>>>>
>>>>> I'll continue investigation but it would be nice if someone will try
>>>>> to investigate it in the same time.
>>>>>
>>>>> Thanks in advance.
>>>>>
>>>>> SY, Alexey
>>>>>
>>>> Yes, it is a serious regression. And do you know when it start to fail?
>>>> I will try it when I go to office tomorrow since I have no classlib
>>>> on hand. Not sure whether I can help.:)
>>> FYI: It's working ok for me on the current HEAD of classlib (r572680)
>>> with the IBM VME.
>>>
>>> Regards,
>>> Tim
>>>
>
--
Gregory
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Alexey Petrenko <al...@gmail.com>.
Forget to say: windowsXP - release build
2007/9/4, Alexey Petrenko <al...@gmail.com>:
> Yes, looks like we really have a regression.
> I've tried Eclipse with M2 and recent classlib with j9 and works in
> both cases. But silently crashes silently in the very beging. Even
> without trace in configuration directory.
>
> So we need to investigate the issue.
>
> Any help is welcome :)
>
> SY, Alexey
>
> 2007/9/4, Tim Ellison <t....@gmail.com>:
> > Leo Li wrote:
> > > On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
> > >> Guys,
> > >>
> > >> I've tried to run In Harmony with Eclipse bundle on the recent
> > >> harmony/drlvm build but it crashes silently in the very begining.
> > >> I would say that this is very serious regression for us.
> > >>
> > >> I'll continue investigation but it would be nice if someone will try
> > >> to investigate it in the same time.
> > >>
> > >> Thanks in advance.
> > >>
> > >> SY, Alexey
> > >>
> > >
> > > Yes, it is a serious regression. And do you know when it start to fail?
> > > I will try it when I go to office tomorrow since I have no classlib
> > > on hand. Not sure whether I can help.:)
> >
> > FYI: It's working ok for me on the current HEAD of classlib (r572680)
> > with the IBM VME.
> >
> > Regards,
> > Tim
> >
>
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Alexey Petrenko <al...@gmail.com>.
Yes, looks like we really have a regression.
I've tried Eclipse with M2 and recent classlib with j9 and works in
both cases. But silently crashes silently in the very beging. Even
without trace in configuration directory.
So we need to investigate the issue.
Any help is welcome :)
SY, Alexey
2007/9/4, Tim Ellison <t....@gmail.com>:
> Leo Li wrote:
> > On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
> >> Guys,
> >>
> >> I've tried to run In Harmony with Eclipse bundle on the recent
> >> harmony/drlvm build but it crashes silently in the very begining.
> >> I would say that this is very serious regression for us.
> >>
> >> I'll continue investigation but it would be nice if someone will try
> >> to investigate it in the same time.
> >>
> >> Thanks in advance.
> >>
> >> SY, Alexey
> >>
> >
> > Yes, it is a serious regression. And do you know when it start to fail?
> > I will try it when I go to office tomorrow since I have no classlib
> > on hand. Not sure whether I can help.:)
>
> FYI: It's working ok for me on the current HEAD of classlib (r572680)
> with the IBM VME.
>
> Regards,
> Tim
>
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Tim Ellison <t....@gmail.com>.
Leo Li wrote:
> On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
>> Guys,
>>
>> I've tried to run In Harmony with Eclipse bundle on the recent
>> harmony/drlvm build but it crashes silently in the very begining.
>> I would say that this is very serious regression for us.
>>
>> I'll continue investigation but it would be nice if someone will try
>> to investigate it in the same time.
>>
>> Thanks in advance.
>>
>> SY, Alexey
>>
>
> Yes, it is a serious regression. And do you know when it start to fail?
> I will try it when I go to office tomorrow since I have no classlib
> on hand. Not sure whether I can help.:)
FYI: It's working ok for me on the current HEAD of classlib (r572680)
with the IBM VME.
Regards,
Tim
Re: [eclipse] Eclipse 3.3 crashes on current Harmony
Posted by Leo Li <li...@gmail.com>.
On 9/4/07, Alexey Petrenko <al...@gmail.com> wrote:
> Guys,
>
> I've tried to run In Harmony with Eclipse bundle on the recent
> harmony/drlvm build but it crashes silently in the very begining.
> I would say that this is very serious regression for us.
>
> I'll continue investigation but it would be nice if someone will try
> to investigate it in the same time.
>
> Thanks in advance.
>
> SY, Alexey
>
Yes, it is a serious regression. And do you know when it start to fail?
I will try it when I go to office tomorrow since I have no classlib
on hand. Not sure whether I can help.:)
--
Leo Li
China Software Development Lab, IBM