Home » Archived » Visual Editor (VE) » VE problem with AMD 64 bits
| | | |
| Re: VE problem with AMD 64 bits [message #109195 is a reply to message #109144] |
Sat, 08 October 2005 16:36   |
 Jeff Myers
Messages: 489
Registered: July 2009 |
Senior Member |
|
|
Jose,
This is an extremely odd error. I know that we've successfully run VE
on x86_64/gtk2 for SWT development.
Line 75 of ImageCapture.java is:
image = getImageOfHandle(control.handle, control.getDisplay(),
includeChildren);
where control is the SWT Control class:
http://help.eclipse.org/help31/nftopic/org.eclipse.platform. doc.isv/reference/api/org/eclipse/swt/widgets/Control.html
So the handle field is present in the Control class, but you're getting
a NoSuchFieldError. Weird. No clue how this could happen, or how to
fix it. Anyone else have any ideas?
- Jeff
Jose Freire wrote:
> Still no go...
>
> I'm attaching a screenshot.
>
> You can see on the left, the external draw of designed window, and on
> the right, the VE editor inside Eclipse. The error message next to the
> light bulb is: Get of picture failed: "Handle"
>
> ------------------------------------------------------------ ------------------------------------------
>
> The stack trace is always the same:
> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-07 20:46:51.304
> !MESSAGE In REMCallbackThread
> !STACK 0
> java.lang.NullPointerException
> at
> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>
> at
> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>
> at
> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>
>
> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-07 20:46:51.406
> !MESSAGE
> +++ Warning +++: Fri Oct 07 20:46:51 WEST 2005 Project (Vianobis)-VM
> for Vianobis:err>
> java.lang.NoSuchFieldError: handle
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>
> at
> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>
> at
> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
> at
> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
> org.eclipse.swt.SWTException: Failed to execute runnable
> (java.lang.NoSuchFieldError: handle)
> at org.eclipse.swt.SWT.error(SWT.java:2942)
> at org.eclipse.swt.SWT.error(SWT.java:2865)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>
> at
> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
> at
> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
> Caused by: java.lang.NoSuchFieldError: handle
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>
> at
> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>
> ------------------------------------------------------------ --------------------------------------------
>
>
> I hope this helps!
>
> Thanks,
>
> Zé
>
> Jose Freire wrote:
>
>> Hi Jeff,
>>
>> I'm using the x86_64/gtk2 version of Eclipse.
>>
>> Eclipse 3.1.1 was just out, so I'm going to try with this new version
>> and I'll report back to this list.
>>
>> Thanks,
>>
>> Ze
>>
>> Jeff Myers wrote:
>>
>>> Jose,
>>>
>>> Did you download the x84_64/gtk2 version of Eclipse, or the 32 bit
>>> version?
>>>
>>> - Jeff
>
>
>
> ------------------------------------------------------------ ------------
>
|
|
|
| Re: VE problem with AMD 64 bits [message #109297 is a reply to message #109144] |
Mon, 10 October 2005 17:19 |
Srimanth 
Messages: 225
Registered: July 2009 |
Senior Member |
|
|
Hi Jose,
So what seems to be the problem is that the remote VM is not able to
find the field 'handle' on Control class. By looking at the source of
Eclipse 3.1.1 and 3.2M2 (x86_64), 'handle' is defined in the Widget
class and is present.
We compiled the source into a .class file using Eclipse 3.1 of the x86
platform. It *could* be that it cant find the field because now it is
being run against a x86_64 platform .class file. Whats puzzling is that
the same thing worked for Jeff. So I was wondering as to which VM you
were using?
Also, could you please check which exact SWT plugin is being used for
the project - Right click on 'Standard Widget Toolkit(SWT)'
library>'Configure ...' . Also, please make note if there are multiple
SWT plugins there.
Also, since this is a very generic problem, could you please try to
quickly recreate this using a brand new download, workspace and project?
Just drop a Shell and see if any image comes up.
Hopefully we can narrow down on whats causing this wierd behaviour.
Regards,
Sri.
Jose Freire wrote:
> Still no go...
>
> I'm attaching a screenshot.
>
> You can see on the left, the external draw of designed window, and on
> the right, the VE editor inside Eclipse. The error message next to the
> light bulb is: Get of picture failed: "Handle"
>
> ------------------------------------------------------------ ------------------------------------------
>
> The stack trace is always the same:
> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-07 20:46:51.304
> !MESSAGE In REMCallbackThread
> !STACK 0
> java.lang.NullPointerException
> at
> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>
> at
> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>
> at
> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>
>
> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-07 20:46:51.406
> !MESSAGE
> +++ Warning +++: Fri Oct 07 20:46:51 WEST 2005 Project (Vianobis)-VM
> for Vianobis:err>
> java.lang.NoSuchFieldError: handle
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>
> at
> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>
> at
> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
> at
> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
> org.eclipse.swt.SWTException: Failed to execute runnable
> (java.lang.NoSuchFieldError: handle)
> at org.eclipse.swt.SWT.error(SWT.java:2942)
> at org.eclipse.swt.SWT.error(SWT.java:2865)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>
> at
> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
> at
> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
> Caused by: java.lang.NoSuchFieldError: handle
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>
> at
> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>
> ------------------------------------------------------------ --------------------------------------------
>
>
> I hope this helps!
>
> Thanks,
>
> Zé
>
> Jose Freire wrote:
>
>> Hi Jeff,
>>
>> I'm using the x86_64/gtk2 version of Eclipse.
>>
>> Eclipse 3.1.1 was just out, so I'm going to try with this new version
>> and I'll report back to this list.
>>
>> Thanks,
>>
>> Ze
>>
>> Jeff Myers wrote:
>>
>>> Jose,
>>>
>>> Did you download the x84_64/gtk2 version of Eclipse, or the 32 bit
>>> version?
>>>
>>> - Jeff
>
>
>
> ------------------------------------------------------------ ------------
>
|
|
|
| Re: VE problem with AMD 64 bits [message #109310 is a reply to message #109297] |
Tue, 11 October 2005 00:08 |
José Freire
Messages: 18
Registered: July 2009 |
Junior Member |
|
|
Hi Sri!
Did a fresh install like you said, of Eclipse 3.1.1 (x86_64), with Java
1.5 Update 5 (x86_64), installed VE 1.1 from eclipse update, updated to
VE 1.1.0.1, and uninstalled all the disabled features that got installed
on the way (like EMF 2.1.0, and GEF 3.1.0) and created an empty workspace.
For a moment there, I though the problem was solved, but no.
Try to make any sense of this:
1) Created a Java project
2) Created a Shell class with Visual Editor -> All is Ok, and I almost
replied to this newsgroup with the good news.
But then a did a second test.
1) Created a Plugin project
2) Selected a Plugin project with a view, and let the wizzard create the
framework
3) Opened the view class created by the wizzard in VE and got the error!
4) Created a Composite class inside the project, opened it and got the
error!
5) Created a Shell class inside the project, opened it and everything is
ok, and I can work normally in VE with the Shell Class!
So... why do Shells work, and Composites don't?
But back to my old workspace:
I checked the plugin dependencies like you said, and SWT is pointing to
the x86_64 version when I start eclipse x86_x64.
Created a Shell class, and it worked, like the clean install, so I guess
it isn't a workspace/project problem.
Did this help?
Thanks!
Jose
Sri Gunturi wrote:
> Hi Jose,
> So what seems to be the problem is that the remote VM is not able to
> find the field 'handle' on Control class. By looking at the source of
> Eclipse 3.1.1 and 3.2M2 (x86_64), 'handle' is defined in the Widget
> class and is present.
> We compiled the source into a .class file using Eclipse 3.1 of the
> x86 platform. It *could* be that it cant find the field because now it
> is being run against a x86_64 platform .class file. Whats puzzling is
> that the same thing worked for Jeff. So I was wondering as to which VM
> you were using?
> Also, could you please check which exact SWT plugin is being used
> for the project - Right click on 'Standard Widget Toolkit(SWT)'
> library>'Configure ...' . Also, please make note if there are multiple
> SWT plugins there.
> Also, since this is a very generic problem, could you please try to
> quickly recreate this using a brand new download, workspace and project?
> Just drop a Shell and see if any image comes up.
>
> Hopefully we can narrow down on whats causing this wierd behaviour.
> Regards,
> Sri.
>
>
>
>
> Jose Freire wrote:
>
>> Still no go...
>>
>> I'm attaching a screenshot.
>>
>> You can see on the left, the external draw of designed window, and on
>> the right, the VE editor inside Eclipse. The error message next to the
>> light bulb is: Get of picture failed: "Handle"
>>
>> ------------------------------------------------------------ ------------------------------------------
>>
>> The stack trace is always the same:
>> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-07 20:46:51.304
>> !MESSAGE In REMCallbackThread
>> !STACK 0
>> java.lang.NullPointerException
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>>
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>>
>> at
>> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>>
>>
>> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-07 20:46:51.406
>> !MESSAGE
>> +++ Warning +++: Fri Oct 07 20:46:51 WEST 2005 Project
>> (Vianobis)-VM for Vianobis:err>
>> java.lang.NoSuchFieldError: handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> org.eclipse.swt.SWTException: Failed to execute runnable
>> (java.lang.NoSuchFieldError: handle)
>> at org.eclipse.swt.SWT.error(SWT.java:2942)
>> at org.eclipse.swt.SWT.error(SWT.java:2865)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> Caused by: java.lang.NoSuchFieldError: handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> ------------------------------------------------------------ --------------------------------------------
>>
>>
>> I hope this helps!
>>
>> Thanks,
>>
>> Zé
>>
>> Jose Freire wrote:
>>
>>> Hi Jeff,
>>>
>>> I'm using the x86_64/gtk2 version of Eclipse.
>>>
>>> Eclipse 3.1.1 was just out, so I'm going to try with this new version
>>> and I'll report back to this list.
>>>
>>> Thanks,
>>>
>>> Ze
>>>
>>> Jeff Myers wrote:
>>>
>>>> Jose,
>>>>
>>>> Did you download the x84_64/gtk2 version of Eclipse, or the 32 bit
>>>> version?
>>>>
>>>> - Jeff
>>
>>
>>
>>
>> ------------------------------------------------------------ ------------
>>
|
|
|
| Re: VE problem with AMD 64 bits [message #109380 is a reply to message #109310] |
Wed, 12 October 2005 14:25 |
Srimanth
Messages: 225
Registered: July 2009 |
Senior Member |
|
|
Hi Jose,
Thanks for testing this out. When you say 'I can work normally in VE
with the Shell Class' are you able to drop components on it, set colors,
text, fonts etc. and everything shows up/works fine? And you say this
cant be done with Composite?
Also just to make sure - the errors that you get for the Composite
class, are the same about the missing 'handle' field? Also, are there
any log messages before the missing 'handle' field?
One other test that could be done is to use the 1.4.2 VM and see if it
is able to find the 'handle' field of the Composite class.
Just as a side note, EMF 2.1.0 and GEF 3.1.0 are needed by VE to work -
I am trying to understand how this worked even when you uninstalled them.
It might be better to attach the log that you get on a brand new
workspace when the Composite fails.
Regards,
Sri.
Jose Freire wrote:
> Hi Sri!
>
> Did a fresh install like you said, of Eclipse 3.1.1 (x86_64), with Java
> 1.5 Update 5 (x86_64), installed VE 1.1 from eclipse update, updated to
> VE 1.1.0.1, and uninstalled all the disabled features that got installed
> on the way (like EMF 2.1.0, and GEF 3.1.0) and created an empty workspace.
>
> For a moment there, I though the problem was solved, but no.
>
> Try to make any sense of this:
>
> 1) Created a Java project
> 2) Created a Shell class with Visual Editor -> All is Ok, and I almost
> replied to this newsgroup with the good news.
>
> But then a did a second test.
>
> 1) Created a Plugin project
> 2) Selected a Plugin project with a view, and let the wizzard create the
> framework
> 3) Opened the view class created by the wizzard in VE and got the error!
> 4) Created a Composite class inside the project, opened it and got the
> error!
> 5) Created a Shell class inside the project, opened it and everything is
> ok, and I can work normally in VE with the Shell Class!
>
> So... why do Shells work, and Composites don't?
>
> But back to my old workspace:
> I checked the plugin dependencies like you said, and SWT is pointing to
> the x86_64 version when I start eclipse x86_x64.
> Created a Shell class, and it worked, like the clean install, so I guess
> it isn't a workspace/project problem.
>
> Did this help?
>
> Thanks!
>
> Jose
>
> Sri Gunturi wrote:
>
>> Hi Jose,
>> So what seems to be the problem is that the remote VM is not able
>> to find the field 'handle' on Control class. By looking at the source
>> of Eclipse 3.1.1 and 3.2M2 (x86_64), 'handle' is defined in the Widget
>> class and is present.
>> We compiled the source into a .class file using Eclipse 3.1 of the
>> x86 platform. It *could* be that it cant find the field because now it
>> is being run against a x86_64 platform .class file. Whats puzzling is
>> that the same thing worked for Jeff. So I was wondering as to which VM
>> you were using?
>> Also, could you please check which exact SWT plugin is being used
>> for the project - Right click on 'Standard Widget Toolkit(SWT)'
>> library>'Configure ...' . Also, please make note if there are multiple
>> SWT plugins there.
>> Also, since this is a very generic problem, could you please try
>> to quickly recreate this using a brand new download, workspace and
>> project? Just drop a Shell and see if any image comes up.
>>
>> Hopefully we can narrow down on whats causing this wierd behaviour.
>> Regards,
>> Sri.
>>
>>
>>
>>
>> Jose Freire wrote:
>>
>>> Still no go...
>>>
>>> I'm attaching a screenshot.
>>>
>>> You can see on the left, the external draw of designed window, and on
>>> the right, the VE editor inside Eclipse. The error message next to
>>> the light bulb is: Get of picture failed: "Handle"
>>>
>>> ------------------------------------------------------------ ------------------------------------------
>>>
>>> The stack trace is always the same:
>>> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-07 20:46:51.304
>>> !MESSAGE In REMCallbackThread
>>> !STACK 0
>>> java.lang.NullPointerException
>>> at
>>> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>>>
>>> at
>>> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>>>
>>> at
>>> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>>>
>>>
>>> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-07 20:46:51.406
>>> !MESSAGE
>>> +++ Warning +++: Fri Oct 07 20:46:51 WEST 2005 Project
>>> (Vianobis)-VM for Vianobis:err>
>>> java.lang.NoSuchFieldError: handle
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>>
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>>
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>>
>>> at
>>> org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>> at
>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>>
>>> at
>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>>> at
>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>>
>>> org.eclipse.swt.SWTException: Failed to execute runnable
>>> (java.lang.NoSuchFieldError: handle)
>>> at org.eclipse.swt.SWT.error(SWT.java:2942)
>>> at org.eclipse.swt.SWT.error(SWT.java:2865)
>>> at
>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>>>
>>> at
>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>>> at
>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>>
>>> Caused by: java.lang.NoSuchFieldError: handle
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>>
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>>
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>>
>>> at
>>> org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>> at
>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>>
>>> ------------------------------------------------------------ --------------------------------------------
>>>
>>>
>>> I hope this helps!
>>>
>>> Thanks,
>>>
>>> Zé
>>>
>>> Jose Freire wrote:
>>>
>>>> Hi Jeff,
>>>>
>>>> I'm using the x86_64/gtk2 version of Eclipse.
>>>>
>>>> Eclipse 3.1.1 was just out, so I'm going to try with this new
>>>> version and I'll report back to this list.
>>>>
>>>> Thanks,
>>>>
>>>> Ze
>>>>
>>>> Jeff Myers wrote:
>>>>
>>>>> Jose,
>>>>>
>>>>> Did you download the x84_64/gtk2 version of Eclipse, or the 32 bit
>>>>> version?
>>>>>
>>>>> - Jeff
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------ ------------
>>>
|
|
| |
| Re: VE problem with AMD 64 bits [message #109446 is a reply to message #109431] |
Thu, 13 October 2005 14:41 |
Srimanth
Messages: 225
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------000601020706000500050000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Hi Jose,
Lets try something simple like a small app which just prints the
handles of components. Import the attached SWT app into the project
where you are unable to edit extended Composite using VE. Run the
DisplayHandles.java file as an SWT app and press on the 'Display
Handles' button. This will print the handles of the Shell, the button
you just pressed, a Spinner, a regular Composite, and an extended
Composite to the err stream. Hopefully this simple testcase will work as
it should.
One more thing is that can you check if there are any other classes
named 'org.eclipse.swt.widgets.Composite' in that project's classpath -
just want to make sure that some other class is not being loaded by the
classloader which doesnt have the handle defined in its hierarchy.
Regards,
Sri.
Jose Freire wrote:
> Hi Sri!
>
> When I work with the Shell class I'm able to to everything I tried, like
> dropping components, set colors, etc etc. Everything shows up, and works
> exactly like it should.
>
> Tested it with Java 1.4.2 (I had to test it with IBM 1.4.2 SR2, since
> SUN doesn't have a AMD Athlon 64 version, only a Intel IA64 version),
> and the error is the same (java.lang.NoSuchFieldError:
> org/eclipse/swt/widgets/Control.handle).
>
> I'll attach a subset of 1.4.2 log (since it also gave me a lot of other
> errors relating to deprecated X libs JRE 1.4.2 requires and I'll spare
> you of that! :) )
>
> Regarding EMF 2.1.0, and GEF 3.1.0. I've got EMF 2.1.1 and GEF 3.1.1
> installed. I only uninstalled EMF 2.1.0 and GEF 3.1.0 because they where
> disabled by the upgrade. Sorry if I caused any confusion!
>
> I'm attaching both logs.
>
> Thanks!
>
> Z
|
|
|
| Re: VE problem with AMD 64 bits [message #109566 is a reply to message #109446] |
Thu, 13 October 2005 23:15 |
José Freire
Messages: 18
Registered: July 2009 |
Junior Member |
|
|
Hi Sri!
Tried your code, and although I still have the same error inside Eclipse
(java.lang.NoSuchFieldError: handle) it runs sucessfully as a SWT
application.
The output is:
Shell handle:46913881779552
Button handle:46913881820432
Spinner handle:46913888185536
Green Composite handle:46913888195984
Red Composite handle:46913888263984
There is something that I don't understand:
1) VE renders the actual composite outside Eclipse, and that outside
render is perfect.
2) The code runs sucessfully outside Eclipse as a SWT APP.
Why the "java.lang.NoSuchFieldError: handle" *inside* Eclipse?
I have some things that crossed my mind. It may not make any sense at
all, but maybe we'll get lucky, here it goes:
1) I don't really understand how VE works, but it seems that the
comunication between JVMs in x86_86 mode is not working as it should.
Is VE trying to "grab" the outside render inside the editor, and that
"grabbing" is failing? That would explain the wireframe-like composite
rendering inside VE.
2) I noticed in the source of Control.class that all the functions
returned type "int" and now return type "long". What is the impact in
that change when we're talking 64 bits?
3) I searched this newsgroup and back in May you helped someone with an
error in x86_86 arch relating to Eclipse 3.1M7, and it envolved
"swt-gtk-print". However, the java.lang.NoSuchFieldError was already
present in the logs. Did you noticed that at the time?
Many thanks!
If you can solve this, I'll buy you a beer when you come to visit
Portugal! :)
Zé
Sri Gunturi wrote:
> Hi Jose,
> Lets try something simple like a small app which just prints the
> handles of components. Import the attached SWT app into the project
> where you are unable to edit extended Composite using VE. Run the
> DisplayHandles.java file as an SWT app and press on the 'Display
> Handles' button. This will print the handles of the Shell, the button
> you just pressed, a Spinner, a regular Composite, and an extended
> Composite to the err stream. Hopefully this simple testcase will work as
> it should.
> One more thing is that can you check if there are any other classes
> named 'org.eclipse.swt.widgets.Composite' in that project's classpath -
> just want to make sure that some other class is not being loaded by the
> classloader which doesnt have the handle defined in its hierarchy.
> Regards,
> Sri.
>
>
>
>
> Jose Freire wrote:
>
>> Hi Sri!
>>
>> When I work with the Shell class I'm able to to everything I tried,
>> like dropping components, set colors, etc etc. Everything shows up,
>> and works exactly like it should.
>>
>> Tested it with Java 1.4.2 (I had to test it with IBM 1.4.2 SR2, since
>> SUN doesn't have a AMD Athlon 64 version, only a Intel IA64 version),
>> and the error is the same (java.lang.NoSuchFieldError:
>> org/eclipse/swt/widgets/Control.handle).
>>
>> I'll attach a subset of 1.4.2 log (since it also gave me a lot of
>> other errors relating to deprecated X libs JRE 1.4.2 requires and I'll
>> spare you of that! :) )
>>
>> Regarding EMF 2.1.0, and GEF 3.1.0. I've got EMF 2.1.1 and GEF 3.1.1
>> installed. I only uninstalled EMF 2.1.0 and GEF 3.1.0 because they
>> where disabled by the upgrade. Sorry if I caused any confusion!
>>
>> I'm attaching both logs.
>>
>> Thanks!
>>
>> Zé
>>
>> Sri Gunturi wrote:
>>
>>> Hi Jose,
>>> Thanks for testing this out. When you say 'I can work normally in
>>> VE with the Shell Class' are you able to drop components on it, set
>>> colors, text, fonts etc. and everything shows up/works fine? And you
>>> say this cant be done with Composite?
>>> Also just to make sure - the errors that you get for the
>>> Composite class, are the same about the missing 'handle' field? Also,
>>> are there any log messages before the missing 'handle' field?
>>> One other test that could be done is to use the 1.4.2 VM and see
>>> if it is able to find the 'handle' field of the Composite class.
>>> Just as a side note, EMF 2.1.0 and GEF 3.1.0 are needed by VE to
>>> work - I am trying to understand how this worked even when you
>>> uninstalled them.
>>> It might be better to attach the log that you get on a brand new
>>> workspace when the Composite fails.
>>> Regards,
>>> Sri.
>>>
>>>
>>>
>>> Jose Freire wrote:
>>>
>>>> Hi Sri!
>>>>
>>>> Did a fresh install like you said, of Eclipse 3.1.1 (x86_64), with
>>>> Java 1.5 Update 5 (x86_64), installed VE 1.1 from eclipse update,
>>>> updated to VE 1.1.0.1, and uninstalled all the disabled features
>>>> that got installed on the way (like EMF 2.1.0, and GEF 3.1.0) and
>>>> created an empty workspace.
>>>>
>>>> For a moment there, I though the problem was solved, but no.
>>>>
>>>> Try to make any sense of this:
>>>>
>>>> 1) Created a Java project
>>>> 2) Created a Shell class with Visual Editor -> All is Ok, and I
>>>> almost replied to this newsgroup with the good news.
>>>>
>>>> But then a did a second test.
>>>>
>>>> 1) Created a Plugin project
>>>> 2) Selected a Plugin project with a view, and let the wizzard create
>>>> the framework
>>>> 3) Opened the view class created by the wizzard in VE and got the
>>>> error!
>>>> 4) Created a Composite class inside the project, opened it and got
>>>> the error!
>>>> 5) Created a Shell class inside the project, opened it and
>>>> everything is ok, and I can work normally in VE with the Shell Class!
>>>>
>>>> So... why do Shells work, and Composites don't?
>>>>
>>>> But back to my old workspace:
>>>> I checked the plugin dependencies like you said, and SWT is pointing
>>>> to the x86_64 version when I start eclipse x86_x64.
>>>> Created a Shell class, and it worked, like the clean install, so I
>>>> guess it isn't a workspace/project problem.
>>>>
>>>> Did this help?
>>>>
>>>> Thanks!
>>>>
>>>> Jose
>>>>
>>>> Sri Gunturi wrote:
>>>>
>>>>> Hi Jose,
>>>>> So what seems to be the problem is that the remote VM is not
>>>>> able to find the field 'handle' on Control class. By looking at the
>>>>> source of Eclipse 3.1.1 and 3.2M2 (x86_64), 'handle' is defined in
>>>>> the Widget class and is present.
>>>>> We compiled the source into a .class file using Eclipse 3.1 of
>>>>> the x86 platform. It *could* be that it cant find the field because
>>>>> now it is being run against a x86_64 platform .class file. Whats
>>>>> puzzling is that the same thing worked for Jeff. So I was wondering
>>>>> as to which VM you were using?
>>>>> Also, could you please check which exact SWT plugin is being
>>>>> used for the project - Right click on 'Standard Widget
>>>>> Toolkit(SWT)' library>'Configure ...' . Also, please make note if
>>>>> there are multiple SWT plugins there.
>>>>> Also, since this is a very generic problem, could you please
>>>>> try to quickly recreate this using a brand new download, workspace
>>>>> and project? Just drop a Shell and see if any image comes up.
>>>>>
>>>>> Hopefully we can narrow down on whats causing this wierd behaviour.
>>>>> Regards,
>>>>> Sri.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Jose Freire wrote:
>>>>>
>>>>>> Still no go...
>>>>>>
>>>>>> I'm attaching a screenshot.
>>>>>>
>>>>>> You can see on the left, the external draw of designed window, and
>>>>>> on the right, the VE editor inside Eclipse. The error message next
>>>>>> to the light bulb is: Get of picture failed: "Handle"
>>>>>>
>>>>>> ------------------------------------------------------------ ------------------------------------------
>>>>>>
>>>>>> The stack trace is always the same:
>>>>>> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-07 20:46:51.304
>>>>>> !MESSAGE In REMCallbackThread
>>>>>> !STACK 0
>>>>>> java.lang.NullPointerException
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>>>>>>
>>>>>>
>>>>>> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-07 20:46:51.406
>>>>>> !MESSAGE
>>>>>> +++ Warning +++: Fri Oct 07 20:46:51 WEST 2005 Project
>>>>>> (Vianobis)-VM for Vianobis:err>
>>>>>> java.lang.NoSuchFieldError: handle
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>>>>>
>>>>>> org.eclipse.swt.SWTException: Failed to execute runnable
>>>>>> (java.lang.NoSuchFieldError: handle)
>>>>>> at org.eclipse.swt.SWT.error(SWT.java:2942)
>>>>>> at org.eclipse.swt.SWT.error(SWT.java:2865)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>>>>>
>>>>>> Caused by: java.lang.NoSuchFieldError: handle
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>>>>>
>>>>>> ------------------------------------------------------------ --------------------------------------------
>>>>>>
>>>>>>
>>>>>> I hope this helps!
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Zé
>>>>>>
>>>>>> Jose Freire wrote:
>>>>>>
>>>>>>> Hi Jeff,
>>>>>>>
>>>>>>> I'm using the x86_64/gtk2 version of Eclipse.
>>>>>>>
>>>>>>> Eclipse 3.1.1 was just out, so I'm going to try with this new
>>>>>>> version and I'll report back to this list.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Ze
>>>>>>>
>>>>>>> Jeff Myers wrote:
>>>>>>>
>>>>>>>> Jose,
>>>>>>>>
>>>>>>>> Did you download the x84_64/gtk2 version of Eclipse, or the 32
>>>>>>>> bit version?
>>>>>>>>
>>>>>>>> - Jeff
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------ ------------
>>>>>>
>>>>>>
>>
>>
>> ------------------------------------------------------------ ------------
>>
>> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-13 00:07:18.746
>> !MESSAGE In REMCallbackThread
>> !STACK 0
>> java.lang.NullPointerException
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>>
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>>
>> at
>> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>>
>>
>> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-13 00:07:18.864
>> !MESSAGE +++ Warning +++: Thu Oct 13 00:07:18 WEST 2005 Project
>> (VeTest)-VM for VeTest:err>
>> java.lang.NoSuchFieldError: org/eclipse/swt/widgets/Control.handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> org.eclipse.swt.SWTException: Failed to execute runnable
>> (java.lang.NoSuchFieldError: org/eclipse/swt/widgets/Control.handle)
>> at org.eclipse.swt.SWT.error(SWT.java:2942)
>> at org.eclipse.swt.SWT.error(SWT.java:2865)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> Caused by: java.lang.NoSuchFieldError:
>> org/eclipse/swt/widgets/Control.handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>>
>>
>> ------------------------------------------------------------ ------------
>>
>> !SESSION 2005-10-13 00:18:04.437
>> -----------------------------------------------
>> eclipse.buildId=M20050929-0840
>> java.version=1.5.0_05
>> java.vendor=Sun Microsystems Inc.
>> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
>> Command-line arguments: -os linux -ws gtk -arch x86_64
>>
>> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-13 00:18:28.178
>> !MESSAGE In REMCallbackThread
>> !STACK 0
>> java.lang.NullPointerException
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>>
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>>
>> at
>> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>>
>>
>> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-13 00:18:28.281
>> !MESSAGE +++ Warning +++: Thu Oct 13 00:18:28 WEST 2005 Project
>> (VeTest)-VM for VeTest:err>
>> java.lang.NoSuchFieldError: handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> org.eclipse.swt.SWTException: Failed to execute runnable
>> (java.lang.NoSuchFieldError: handle)
>> at org.eclipse.swt.SWT.error(SWT.java:2942)
>> at org.eclipse.swt.SWT.error(SWT.java:2865)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> Caused by: java.lang.NoSuchFieldError: handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> ... 3 more
>
>
|
|
| | | | |
| Re: VE problem with AMD 64 bits [message #610947 is a reply to message #109144] |
Sat, 08 October 2005 16:36 |
Jeff Myers
Messages: 489
Registered: July 2009 |
Senior Member |
|
|
Jose,
This is an extremely odd error. I know that we've successfully run VE
on x86_64/gtk2 for SWT development.
Line 75 of ImageCapture.java is:
image = getImageOfHandle(control.handle, control.getDisplay(),
includeChildren);
where control is the SWT Control class:
http://help.eclipse.org/help31/nftopic/org.eclipse.platform. doc.isv/reference/api/org/eclipse/swt/widgets/Control.html
So the handle field is present in the Control class, but you're getting
a NoSuchFieldError. Weird. No clue how this could happen, or how to
fix it. Anyone else have any ideas?
- Jeff
Jose Freire wrote:
> Still no go...
>
> I'm attaching a screenshot.
>
> You can see on the left, the external draw of designed window, and on
> the right, the VE editor inside Eclipse. The error message next to the
> light bulb is: Get of picture failed: "Handle"
>
> ------------------------------------------------------------ ------------------------------------------
>
> The stack trace is always the same:
> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-07 20:46:51.304
> !MESSAGE In REMCallbackThread
> !STACK 0
> java.lang.NullPointerException
> at
> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>
> at
> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>
> at
> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>
>
> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-07 20:46:51.406
> !MESSAGE
> +++ Warning +++: Fri Oct 07 20:46:51 WEST 2005 Project (Vianobis)-VM
> for Vianobis:err>
> java.lang.NoSuchFieldError: handle
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>
> at
> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>
> at
> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
> at
> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
> org.eclipse.swt.SWTException: Failed to execute runnable
> (java.lang.NoSuchFieldError: handle)
> at org.eclipse.swt.SWT.error(SWT.java:2942)
> at org.eclipse.swt.SWT.error(SWT.java:2865)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>
> at
> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
> at
> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
> Caused by: java.lang.NoSuchFieldError: handle
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>
> at
> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>
> ------------------------------------------------------------ --------------------------------------------
>
>
> I hope this helps!
>
> Thanks,
>
> Zé
>
> Jose Freire wrote:
>
>> Hi Jeff,
>>
>> I'm using the x86_64/gtk2 version of Eclipse.
>>
>> Eclipse 3.1.1 was just out, so I'm going to try with this new version
>> and I'll report back to this list.
>>
>> Thanks,
>>
>> Ze
>>
>> Jeff Myers wrote:
>>
>>> Jose,
>>>
>>> Did you download the x84_64/gtk2 version of Eclipse, or the 32 bit
>>> version?
>>>
>>> - Jeff
>
>
>
> ------------------------------------------------------------ ------------
>
|
|
|
| Re: VE problem with AMD 64 bits [message #611161 is a reply to message #109144] |
Mon, 10 October 2005 17:19 |
Srimanth
Messages: 225
Registered: July 2009 |
Senior Member |
|
|
Hi Jose,
So what seems to be the problem is that the remote VM is not able to
find the field 'handle' on Control class. By looking at the source of
Eclipse 3.1.1 and 3.2M2 (x86_64), 'handle' is defined in the Widget
class and is present.
We compiled the source into a .class file using Eclipse 3.1 of the x86
platform. It *could* be that it cant find the field because now it is
being run against a x86_64 platform .class file. Whats puzzling is that
the same thing worked for Jeff. So I was wondering as to which VM you
were using?
Also, could you please check which exact SWT plugin is being used for
the project - Right click on 'Standard Widget Toolkit(SWT)'
library>'Configure ...' . Also, please make note if there are multiple
SWT plugins there.
Also, since this is a very generic problem, could you please try to
quickly recreate this using a brand new download, workspace and project?
Just drop a Shell and see if any image comes up.
Hopefully we can narrow down on whats causing this wierd behaviour.
Regards,
Sri.
Jose Freire wrote:
> Still no go...
>
> I'm attaching a screenshot.
>
> You can see on the left, the external draw of designed window, and on
> the right, the VE editor inside Eclipse. The error message next to the
> light bulb is: Get of picture failed: "Handle"
>
> ------------------------------------------------------------ ------------------------------------------
>
> The stack trace is always the same:
> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-07 20:46:51.304
> !MESSAGE In REMCallbackThread
> !STACK 0
> java.lang.NullPointerException
> at
> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>
> at
> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>
> at
> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>
>
> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-07 20:46:51.406
> !MESSAGE
> +++ Warning +++: Fri Oct 07 20:46:51 WEST 2005 Project (Vianobis)-VM
> for Vianobis:err>
> java.lang.NoSuchFieldError: handle
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>
> at
> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>
> at
> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
> at
> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
> org.eclipse.swt.SWTException: Failed to execute runnable
> (java.lang.NoSuchFieldError: handle)
> at org.eclipse.swt.SWT.error(SWT.java:2942)
> at org.eclipse.swt.SWT.error(SWT.java:2865)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>
> at
> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
> at
> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
> Caused by: java.lang.NoSuchFieldError: handle
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>
> at
> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>
> at
> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>
> ------------------------------------------------------------ --------------------------------------------
>
>
> I hope this helps!
>
> Thanks,
>
> Zé
>
> Jose Freire wrote:
>
>> Hi Jeff,
>>
>> I'm using the x86_64/gtk2 version of Eclipse.
>>
>> Eclipse 3.1.1 was just out, so I'm going to try with this new version
>> and I'll report back to this list.
>>
>> Thanks,
>>
>> Ze
>>
>> Jeff Myers wrote:
>>
>>> Jose,
>>>
>>> Did you download the x84_64/gtk2 version of Eclipse, or the 32 bit
>>> version?
>>>
>>> - Jeff
>
>
>
> ------------------------------------------------------------ ------------
>
|
|
|
| Re: VE problem with AMD 64 bits [message #611163 is a reply to message #109297] |
Tue, 11 October 2005 00:08 |
José Freire
Messages: 18
Registered: July 2009 |
Junior Member |
|
|
Hi Sri!
Did a fresh install like you said, of Eclipse 3.1.1 (x86_64), with Java
1.5 Update 5 (x86_64), installed VE 1.1 from eclipse update, updated to
VE 1.1.0.1, and uninstalled all the disabled features that got installed
on the way (like EMF 2.1.0, and GEF 3.1.0) and created an empty workspace.
For a moment there, I though the problem was solved, but no.
Try to make any sense of this:
1) Created a Java project
2) Created a Shell class with Visual Editor -> All is Ok, and I almost
replied to this newsgroup with the good news.
But then a did a second test.
1) Created a Plugin project
2) Selected a Plugin project with a view, and let the wizzard create the
framework
3) Opened the view class created by the wizzard in VE and got the error!
4) Created a Composite class inside the project, opened it and got the
error!
5) Created a Shell class inside the project, opened it and everything is
ok, and I can work normally in VE with the Shell Class!
So... why do Shells work, and Composites don't?
But back to my old workspace:
I checked the plugin dependencies like you said, and SWT is pointing to
the x86_64 version when I start eclipse x86_x64.
Created a Shell class, and it worked, like the clean install, so I guess
it isn't a workspace/project problem.
Did this help?
Thanks!
Jose
Sri Gunturi wrote:
> Hi Jose,
> So what seems to be the problem is that the remote VM is not able to
> find the field 'handle' on Control class. By looking at the source of
> Eclipse 3.1.1 and 3.2M2 (x86_64), 'handle' is defined in the Widget
> class and is present.
> We compiled the source into a .class file using Eclipse 3.1 of the
> x86 platform. It *could* be that it cant find the field because now it
> is being run against a x86_64 platform .class file. Whats puzzling is
> that the same thing worked for Jeff. So I was wondering as to which VM
> you were using?
> Also, could you please check which exact SWT plugin is being used
> for the project - Right click on 'Standard Widget Toolkit(SWT)'
> library>'Configure ...' . Also, please make note if there are multiple
> SWT plugins there.
> Also, since this is a very generic problem, could you please try to
> quickly recreate this using a brand new download, workspace and project?
> Just drop a Shell and see if any image comes up.
>
> Hopefully we can narrow down on whats causing this wierd behaviour.
> Regards,
> Sri.
>
>
>
>
> Jose Freire wrote:
>
>> Still no go...
>>
>> I'm attaching a screenshot.
>>
>> You can see on the left, the external draw of designed window, and on
>> the right, the VE editor inside Eclipse. The error message next to the
>> light bulb is: Get of picture failed: "Handle"
>>
>> ------------------------------------------------------------ ------------------------------------------
>>
>> The stack trace is always the same:
>> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-07 20:46:51.304
>> !MESSAGE In REMCallbackThread
>> !STACK 0
>> java.lang.NullPointerException
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>>
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>>
>> at
>> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>>
>>
>> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-07 20:46:51.406
>> !MESSAGE
>> +++ Warning +++: Fri Oct 07 20:46:51 WEST 2005 Project
>> (Vianobis)-VM for Vianobis:err>
>> java.lang.NoSuchFieldError: handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> org.eclipse.swt.SWTException: Failed to execute runnable
>> (java.lang.NoSuchFieldError: handle)
>> at org.eclipse.swt.SWT.error(SWT.java:2942)
>> at org.eclipse.swt.SWT.error(SWT.java:2865)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> Caused by: java.lang.NoSuchFieldError: handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> ------------------------------------------------------------ --------------------------------------------
>>
>>
>> I hope this helps!
>>
>> Thanks,
>>
>> Zé
>>
>> Jose Freire wrote:
>>
>>> Hi Jeff,
>>>
>>> I'm using the x86_64/gtk2 version of Eclipse.
>>>
>>> Eclipse 3.1.1 was just out, so I'm going to try with this new version
>>> and I'll report back to this list.
>>>
>>> Thanks,
>>>
>>> Ze
>>>
>>> Jeff Myers wrote:
>>>
>>>> Jose,
>>>>
>>>> Did you download the x84_64/gtk2 version of Eclipse, or the 32 bit
>>>> version?
>>>>
>>>> - Jeff
>>
>>
>>
>>
>> ------------------------------------------------------------ ------------
>>
|
|
|
| Re: VE problem with AMD 64 bits [message #611175 is a reply to message #109310] |
Wed, 12 October 2005 14:25 |
Srimanth
Messages: 225
Registered: July 2009 |
Senior Member |
|
|
Hi Jose,
Thanks for testing this out. When you say 'I can work normally in VE
with the Shell Class' are you able to drop components on it, set colors,
text, fonts etc. and everything shows up/works fine? And you say this
cant be done with Composite?
Also just to make sure - the errors that you get for the Composite
class, are the same about the missing 'handle' field? Also, are there
any log messages before the missing 'handle' field?
One other test that could be done is to use the 1.4.2 VM and see if it
is able to find the 'handle' field of the Composite class.
Just as a side note, EMF 2.1.0 and GEF 3.1.0 are needed by VE to work -
I am trying to understand how this worked even when you uninstalled them.
It might be better to attach the log that you get on a brand new
workspace when the Composite fails.
Regards,
Sri.
Jose Freire wrote:
> Hi Sri!
>
> Did a fresh install like you said, of Eclipse 3.1.1 (x86_64), with Java
> 1.5 Update 5 (x86_64), installed VE 1.1 from eclipse update, updated to
> VE 1.1.0.1, and uninstalled all the disabled features that got installed
> on the way (like EMF 2.1.0, and GEF 3.1.0) and created an empty workspace.
>
> For a moment there, I though the problem was solved, but no.
>
> Try to make any sense of this:
>
> 1) Created a Java project
> 2) Created a Shell class with Visual Editor -> All is Ok, and I almost
> replied to this newsgroup with the good news.
>
> But then a did a second test.
>
> 1) Created a Plugin project
> 2) Selected a Plugin project with a view, and let the wizzard create the
> framework
> 3) Opened the view class created by the wizzard in VE and got the error!
> 4) Created a Composite class inside the project, opened it and got the
> error!
> 5) Created a Shell class inside the project, opened it and everything is
> ok, and I can work normally in VE with the Shell Class!
>
> So... why do Shells work, and Composites don't?
>
> But back to my old workspace:
> I checked the plugin dependencies like you said, and SWT is pointing to
> the x86_64 version when I start eclipse x86_x64.
> Created a Shell class, and it worked, like the clean install, so I guess
> it isn't a workspace/project problem.
>
> Did this help?
>
> Thanks!
>
> Jose
>
> Sri Gunturi wrote:
>
>> Hi Jose,
>> So what seems to be the problem is that the remote VM is not able
>> to find the field 'handle' on Control class. By looking at the source
>> of Eclipse 3.1.1 and 3.2M2 (x86_64), 'handle' is defined in the Widget
>> class and is present.
>> We compiled the source into a .class file using Eclipse 3.1 of the
>> x86 platform. It *could* be that it cant find the field because now it
>> is being run against a x86_64 platform .class file. Whats puzzling is
>> that the same thing worked for Jeff. So I was wondering as to which VM
>> you were using?
>> Also, could you please check which exact SWT plugin is being used
>> for the project - Right click on 'Standard Widget Toolkit(SWT)'
>> library>'Configure ...' . Also, please make note if there are multiple
>> SWT plugins there.
>> Also, since this is a very generic problem, could you please try
>> to quickly recreate this using a brand new download, workspace and
>> project? Just drop a Shell and see if any image comes up.
>>
>> Hopefully we can narrow down on whats causing this wierd behaviour.
>> Regards,
>> Sri.
>>
>>
>>
>>
>> Jose Freire wrote:
>>
>>> Still no go...
>>>
>>> I'm attaching a screenshot.
>>>
>>> You can see on the left, the external draw of designed window, and on
>>> the right, the VE editor inside Eclipse. The error message next to
>>> the light bulb is: Get of picture failed: "Handle"
>>>
>>> ------------------------------------------------------------ ------------------------------------------
>>>
>>> The stack trace is always the same:
>>> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-07 20:46:51.304
>>> !MESSAGE In REMCallbackThread
>>> !STACK 0
>>> java.lang.NullPointerException
>>> at
>>> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>>>
>>> at
>>> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>>>
>>> at
>>> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>>>
>>>
>>> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-07 20:46:51.406
>>> !MESSAGE
>>> +++ Warning +++: Fri Oct 07 20:46:51 WEST 2005 Project
>>> (Vianobis)-VM for Vianobis:err>
>>> java.lang.NoSuchFieldError: handle
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>>
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>>
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>>
>>> at
>>> org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>> at
>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>>
>>> at
>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>>> at
>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>>
>>> org.eclipse.swt.SWTException: Failed to execute runnable
>>> (java.lang.NoSuchFieldError: handle)
>>> at org.eclipse.swt.SWT.error(SWT.java:2942)
>>> at org.eclipse.swt.SWT.error(SWT.java:2865)
>>> at
>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>>>
>>> at
>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>>> at
>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>>
>>> Caused by: java.lang.NoSuchFieldError: handle
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>>
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>>
>>> at
>>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>>
>>> at
>>> org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>> at
>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>>
>>> ------------------------------------------------------------ --------------------------------------------
>>>
>>>
>>> I hope this helps!
>>>
>>> Thanks,
>>>
>>> Zé
>>>
>>> Jose Freire wrote:
>>>
>>>> Hi Jeff,
>>>>
>>>> I'm using the x86_64/gtk2 version of Eclipse.
>>>>
>>>> Eclipse 3.1.1 was just out, so I'm going to try with this new
>>>> version and I'll report back to this list.
>>>>
>>>> Thanks,
>>>>
>>>> Ze
>>>>
>>>> Jeff Myers wrote:
>>>>
>>>>> Jose,
>>>>>
>>>>> Did you download the x84_64/gtk2 version of Eclipse, or the 32 bit
>>>>> version?
>>>>>
>>>>> - Jeff
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------ ------------
>>>
|
|
| |
| Re: VE problem with AMD 64 bits [message #611183 is a reply to message #109431] |
Thu, 13 October 2005 14:41 |
Srimanth
Messages: 225
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------000601020706000500050000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Hi Jose,
Lets try something simple like a small app which just prints the
handles of components. Import the attached SWT app into the project
where you are unable to edit extended Composite using VE. Run the
DisplayHandles.java file as an SWT app and press on the 'Display
Handles' button. This will print the handles of the Shell, the button
you just pressed, a Spinner, a regular Composite, and an extended
Composite to the err stream. Hopefully this simple testcase will work as
it should.
One more thing is that can you check if there are any other classes
named 'org.eclipse.swt.widgets.Composite' in that project's classpath -
just want to make sure that some other class is not being loaded by the
classloader which doesnt have the handle defined in its hierarchy.
Regards,
Sri.
Jose Freire wrote:
> Hi Sri!
>
> When I work with the Shell class I'm able to to everything I tried, like
> dropping components, set colors, etc etc. Everything shows up, and works
> exactly like it should.
>
> Tested it with Java 1.4.2 (I had to test it with IBM 1.4.2 SR2, since
> SUN doesn't have a AMD Athlon 64 version, only a Intel IA64 version),
> and the error is the same (java.lang.NoSuchFieldError:
> org/eclipse/swt/widgets/Control.handle).
>
> I'll attach a subset of 1.4.2 log (since it also gave me a lot of other
> errors relating to deprecated X libs JRE 1.4.2 requires and I'll spare
> you of that! :) )
>
> Regarding EMF 2.1.0, and GEF 3.1.0. I've got EMF 2.1.1 and GEF 3.1.1
> installed. I only uninstalled EMF 2.1.0 and GEF 3.1.0 because they where
> disabled by the upgrade. Sorry if I caused any confusion!
>
> I'm attaching both logs.
>
> Thanks!
>
> Z
|
|
|
| Re: VE problem with AMD 64 bits [message #611197 is a reply to message #109446] |
Thu, 13 October 2005 23:15 |
José Freire
Messages: 18
Registered: July 2009 |
Junior Member |
|
|
Hi Sri!
Tried your code, and although I still have the same error inside Eclipse
(java.lang.NoSuchFieldError: handle) it runs sucessfully as a SWT
application.
The output is:
Shell handle:46913881779552
Button handle:46913881820432
Spinner handle:46913888185536
Green Composite handle:46913888195984
Red Composite handle:46913888263984
There is something that I don't understand:
1) VE renders the actual composite outside Eclipse, and that outside
render is perfect.
2) The code runs sucessfully outside Eclipse as a SWT APP.
Why the "java.lang.NoSuchFieldError: handle" *inside* Eclipse?
I have some things that crossed my mind. It may not make any sense at
all, but maybe we'll get lucky, here it goes:
1) I don't really understand how VE works, but it seems that the
comunication between JVMs in x86_86 mode is not working as it should.
Is VE trying to "grab" the outside render inside the editor, and that
"grabbing" is failing? That would explain the wireframe-like composite
rendering inside VE.
2) I noticed in the source of Control.class that all the functions
returned type "int" and now return type "long". What is the impact in
that change when we're talking 64 bits?
3) I searched this newsgroup and back in May you helped someone with an
error in x86_86 arch relating to Eclipse 3.1M7, and it envolved
"swt-gtk-print". However, the java.lang.NoSuchFieldError was already
present in the logs. Did you noticed that at the time?
Many thanks!
If you can solve this, I'll buy you a beer when you come to visit
Portugal! :)
Zé
Sri Gunturi wrote:
> Hi Jose,
> Lets try something simple like a small app which just prints the
> handles of components. Import the attached SWT app into the project
> where you are unable to edit extended Composite using VE. Run the
> DisplayHandles.java file as an SWT app and press on the 'Display
> Handles' button. This will print the handles of the Shell, the button
> you just pressed, a Spinner, a regular Composite, and an extended
> Composite to the err stream. Hopefully this simple testcase will work as
> it should.
> One more thing is that can you check if there are any other classes
> named 'org.eclipse.swt.widgets.Composite' in that project's classpath -
> just want to make sure that some other class is not being loaded by the
> classloader which doesnt have the handle defined in its hierarchy.
> Regards,
> Sri.
>
>
>
>
> Jose Freire wrote:
>
>> Hi Sri!
>>
>> When I work with the Shell class I'm able to to everything I tried,
>> like dropping components, set colors, etc etc. Everything shows up,
>> and works exactly like it should.
>>
>> Tested it with Java 1.4.2 (I had to test it with IBM 1.4.2 SR2, since
>> SUN doesn't have a AMD Athlon 64 version, only a Intel IA64 version),
>> and the error is the same (java.lang.NoSuchFieldError:
>> org/eclipse/swt/widgets/Control.handle).
>>
>> I'll attach a subset of 1.4.2 log (since it also gave me a lot of
>> other errors relating to deprecated X libs JRE 1.4.2 requires and I'll
>> spare you of that! :) )
>>
>> Regarding EMF 2.1.0, and GEF 3.1.0. I've got EMF 2.1.1 and GEF 3.1.1
>> installed. I only uninstalled EMF 2.1.0 and GEF 3.1.0 because they
>> where disabled by the upgrade. Sorry if I caused any confusion!
>>
>> I'm attaching both logs.
>>
>> Thanks!
>>
>> Zé
>>
>> Sri Gunturi wrote:
>>
>>> Hi Jose,
>>> Thanks for testing this out. When you say 'I can work normally in
>>> VE with the Shell Class' are you able to drop components on it, set
>>> colors, text, fonts etc. and everything shows up/works fine? And you
>>> say this cant be done with Composite?
>>> Also just to make sure - the errors that you get for the
>>> Composite class, are the same about the missing 'handle' field? Also,
>>> are there any log messages before the missing 'handle' field?
>>> One other test that could be done is to use the 1.4.2 VM and see
>>> if it is able to find the 'handle' field of the Composite class.
>>> Just as a side note, EMF 2.1.0 and GEF 3.1.0 are needed by VE to
>>> work - I am trying to understand how this worked even when you
>>> uninstalled them.
>>> It might be better to attach the log that you get on a brand new
>>> workspace when the Composite fails.
>>> Regards,
>>> Sri.
>>>
>>>
>>>
>>> Jose Freire wrote:
>>>
>>>> Hi Sri!
>>>>
>>>> Did a fresh install like you said, of Eclipse 3.1.1 (x86_64), with
>>>> Java 1.5 Update 5 (x86_64), installed VE 1.1 from eclipse update,
>>>> updated to VE 1.1.0.1, and uninstalled all the disabled features
>>>> that got installed on the way (like EMF 2.1.0, and GEF 3.1.0) and
>>>> created an empty workspace.
>>>>
>>>> For a moment there, I though the problem was solved, but no.
>>>>
>>>> Try to make any sense of this:
>>>>
>>>> 1) Created a Java project
>>>> 2) Created a Shell class with Visual Editor -> All is Ok, and I
>>>> almost replied to this newsgroup with the good news.
>>>>
>>>> But then a did a second test.
>>>>
>>>> 1) Created a Plugin project
>>>> 2) Selected a Plugin project with a view, and let the wizzard create
>>>> the framework
>>>> 3) Opened the view class created by the wizzard in VE and got the
>>>> error!
>>>> 4) Created a Composite class inside the project, opened it and got
>>>> the error!
>>>> 5) Created a Shell class inside the project, opened it and
>>>> everything is ok, and I can work normally in VE with the Shell Class!
>>>>
>>>> So... why do Shells work, and Composites don't?
>>>>
>>>> But back to my old workspace:
>>>> I checked the plugin dependencies like you said, and SWT is pointing
>>>> to the x86_64 version when I start eclipse x86_x64.
>>>> Created a Shell class, and it worked, like the clean install, so I
>>>> guess it isn't a workspace/project problem.
>>>>
>>>> Did this help?
>>>>
>>>> Thanks!
>>>>
>>>> Jose
>>>>
>>>> Sri Gunturi wrote:
>>>>
>>>>> Hi Jose,
>>>>> So what seems to be the problem is that the remote VM is not
>>>>> able to find the field 'handle' on Control class. By looking at the
>>>>> source of Eclipse 3.1.1 and 3.2M2 (x86_64), 'handle' is defined in
>>>>> the Widget class and is present.
>>>>> We compiled the source into a .class file using Eclipse 3.1 of
>>>>> the x86 platform. It *could* be that it cant find the field because
>>>>> now it is being run against a x86_64 platform .class file. Whats
>>>>> puzzling is that the same thing worked for Jeff. So I was wondering
>>>>> as to which VM you were using?
>>>>> Also, could you please check which exact SWT plugin is being
>>>>> used for the project - Right click on 'Standard Widget
>>>>> Toolkit(SWT)' library>'Configure ...' . Also, please make note if
>>>>> there are multiple SWT plugins there.
>>>>> Also, since this is a very generic problem, could you please
>>>>> try to quickly recreate this using a brand new download, workspace
>>>>> and project? Just drop a Shell and see if any image comes up.
>>>>>
>>>>> Hopefully we can narrow down on whats causing this wierd behaviour.
>>>>> Regards,
>>>>> Sri.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Jose Freire wrote:
>>>>>
>>>>>> Still no go...
>>>>>>
>>>>>> I'm attaching a screenshot.
>>>>>>
>>>>>> You can see on the left, the external draw of designed window, and
>>>>>> on the right, the VE editor inside Eclipse. The error message next
>>>>>> to the light bulb is: Get of picture failed: "Handle"
>>>>>>
>>>>>> ------------------------------------------------------------ ------------------------------------------
>>>>>>
>>>>>> The stack trace is always the same:
>>>>>> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-07 20:46:51.304
>>>>>> !MESSAGE In REMCallbackThread
>>>>>> !STACK 0
>>>>>> java.lang.NullPointerException
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>>>>>>
>>>>>>
>>>>>> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-07 20:46:51.406
>>>>>> !MESSAGE
>>>>>> +++ Warning +++: Fri Oct 07 20:46:51 WEST 2005 Project
>>>>>> (Vianobis)-VM for Vianobis:err>
>>>>>> java.lang.NoSuchFieldError: handle
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>>>>>
>>>>>> org.eclipse.swt.SWTException: Failed to execute runnable
>>>>>> (java.lang.NoSuchFieldError: handle)
>>>>>> at org.eclipse.swt.SWT.error(SWT.java:2942)
>>>>>> at org.eclipse.swt.SWT.error(SWT.java:2865)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>>>>>
>>>>>> Caused by: java.lang.NoSuchFieldError: handle
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>>>>>
>>>>>> at
>>>>>> org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>>>>> at
>>>>>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>>>>>
>>>>>> ------------------------------------------------------------ --------------------------------------------
>>>>>>
>>>>>>
>>>>>> I hope this helps!
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Zé
>>>>>>
>>>>>> Jose Freire wrote:
>>>>>>
>>>>>>> Hi Jeff,
>>>>>>>
>>>>>>> I'm using the x86_64/gtk2 version of Eclipse.
>>>>>>>
>>>>>>> Eclipse 3.1.1 was just out, so I'm going to try with this new
>>>>>>> version and I'll report back to this list.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Ze
>>>>>>>
>>>>>>> Jeff Myers wrote:
>>>>>>>
>>>>>>>> Jose,
>>>>>>>>
>>>>>>>> Did you download the x84_64/gtk2 version of Eclipse, or the 32
>>>>>>>> bit version?
>>>>>>>>
>>>>>>>> - Jeff
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------ ------------
>>>>>>
>>>>>>
>>
>>
>> ------------------------------------------------------------ ------------
>>
>> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-13 00:07:18.746
>> !MESSAGE In REMCallbackThread
>> !STACK 0
>> java.lang.NullPointerException
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>>
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>>
>> at
>> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>>
>>
>> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-13 00:07:18.864
>> !MESSAGE +++ Warning +++: Thu Oct 13 00:07:18 WEST 2005 Project
>> (VeTest)-VM for VeTest:err>
>> java.lang.NoSuchFieldError: org/eclipse/swt/widgets/Control.handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> org.eclipse.swt.SWTException: Failed to execute runnable
>> (java.lang.NoSuchFieldError: org/eclipse/swt/widgets/Control.handle)
>> at org.eclipse.swt.SWT.error(SWT.java:2942)
>> at org.eclipse.swt.SWT.error(SWT.java:2865)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> Caused by: java.lang.NoSuchFieldError:
>> org/eclipse/swt/widgets/Control.handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>>
>>
>> ------------------------------------------------------------ ------------
>>
>> !SESSION 2005-10-13 00:18:04.437
>> -----------------------------------------------
>> eclipse.buildId=M20050929-0840
>> java.version=1.5.0_05
>> java.vendor=Sun Microsystems Inc.
>> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
>> Command-line arguments: -os linux -ws gtk -arch x86_64
>>
>> !ENTRY org.eclipse.jem.proxy 4 0 2005-10-13 00:18:28.178
>> !MESSAGE In REMCallbackThread
>> !STACK 0
>> java.lang.NullPointerException
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.createImageDa ta(ImageDataCollector.java:313)
>>
>> at
>> org.eclipse.ve.internal.swt.ImageDataCollector.calledBackStr eam(ImageDataCollector.java:187)
>>
>> at
>> org.eclipse.jem.internal.proxy.remote.REMCallbackThread.run( REMCallbackThread.java:276)
>>
>>
>> !ENTRY org.eclipse.jem.proxy 2 0 2005-10-13 00:18:28.281
>> !MESSAGE +++ Warning +++: Thu Oct 13 00:18:28 WEST 2005 Project
>> (VeTest)-VM for VeTest:err>
>> java.lang.NoSuchFieldError: handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> org.eclipse.swt.SWTException: Failed to execute runnable
>> (java.lang.NoSuchFieldError: handle)
>> at org.eclipse.swt.SWT.error(SWT.java:2942)
>> at org.eclipse.swt.SWT.error(SWT.java:2865)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>>
>> at
>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>> at
>> org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
>>
>> Caused by: java.lang.NoSuchFieldError: handle
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImageOfControl(ImageCapture.java:75)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.unix.bits64.ImageCaptur e.getImage(ImageCapture.java:333)
>>
>> at
>> org.eclipse.ve.internal.swt.targetvm.ImageCapture$1.run(Imag eCapture.java:138)
>>
>> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>> at
>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>>
>> ... 3 more
>
>
|
|
| |
Goto Forum:
Current Time: Sat Apr 20 13:10:13 GMT 2024
Powered by FUDForum. Page generated in 0.06119 seconds |
] 
Search
Help
Register
Login
Home
