[cjohan]

I would love to see AMD 64 support (also known as X86-64 support) for MyEclipse IDE, so that I could use it with my X86-64 version of Eclipse 3.0.1.

I presume I cannot use the 32-bit version of MyEclipse IDE with the 64-bit version of Eclipse.

[Riyad Kalla]

MyEclipse and Eclipse are pure Java, the VM they are run on determines if it is 64-bit or not… SOOO the only reason I can assume you are asking this is because you have compiled Eclipse yourself using GCJ? This is a not a supported setup for MyEclipse (although it might work fine, we just don’t do it around here) and we would (likely) never be in a position to ship precompiled platform-specific builds of MyEclipse with GCJ, so it will always be interpreted.

Have you tried MyEclipse installed against your 64-bit Eclipse install? Does it bomb out?

Maybe if you send us a 64-bit computer we can start testing 😀

[cjohan]

The Eclipse I installed was unzipped from the file eclipse-SDK-3.0.1-linux-gtk-amd64.zip, which I obtained from the eclipse.org web site. I didn’t build it myself. But Eclipse uses the swt.gtk64 toolkit, which has some native code linked to it, I believe.

I haven’t tried MyEclipse with this version yet. I assume it won’t work, but maybe…. I’ll let you know if it works. Just hope it doesn’t mangle Eclipse in some way.

If you need a 64-bit computer, the HP a810n has an AMD 64 and costs less than $750 from some sources. 🙂

[Riyad Kalla]

The Eclipse I installed was unzipped from the file eclipse-SDK-3.0.1-linux-gtk-amd64.zip

Ohh, sorry about that I really didn’t know there was any changes needed for 64-bit computers… give it a whirl and let us know. if it is “official” then we will support it, although I am not aware of any 64-bit talk internally, but our developers tend to know things I don’t 😉

Just hope it doesn’t mangle Eclipse in some way.

Try it with a test workspace, if it borks, just remove MyEclipse and create a new workspace. Creating a new workspace is like “reinstalling” Eclipse products since everything is stored in there.

[cjohan]

Hey! It works! I installed EnterpriseWorkbenchInstaller_030804.bin and it worked with no hitches, though the X86_64-bit version of Eclipse has a few problems of its own which were happening before the install of MyEclipse. Thanks for the suggestion. Well, it’s “official”, so let’s see some support! 🙂

[Riyad Kalla]

Thank you for following up, I’ll let the team know the progress.

[cjohan]

Here is a tip for anyone who wants to try the AMD64 (X86_64) version of Eclipse: Ensure that you have a 64-bit Java SDK. Surprisingly, SUSE 9.2 for the AMD 64 came with a 32-bit JRE — no 64-bit version. This resulted in some misleading error messages at Eclipse startup where it claimed it couldn’t load some jar files that clearly were present in Eclipse. For example:

java.lang.UnsatisfiedLinkError: /usr/local/eclipse/plugins/org.eclipse.swt.gtk64_3.0.1/os/linux/amd64/libswt-pi-gtk-3063.so: /usr/local/eclipse/plugins/org.eclipse.swt.gtk64_3.0.1/os/linux/amd64/libswt-pi-gtk-3063.so: cannot open shared object file:
No such file or directory

After installing Linux AMD64 RPM in self-extracting file (jdk-1_5_0_01-linux-amd64-rpm.bin, 39.16 MB) from the Sun Download Center, the UnsatisfiedLinkError problem went away.

[arjan.tijms]

@cjohan wrote:

Here is a tip for anyone who wants to try the AMD64 (X86_64)
After installing Linux AMD64 RPM in self-extracting file (jdk-1_5_0_01-linux-amd64-rpm.bin, 39.16 MB) from the Sun Download Center, the UnsatisfiedLinkError problem went away.

Were the UnsatisfiedLinkError problems the problems you meant with:

though the X86_64-bit version of Eclipse has a few problems of its own which were happening before the install of MyEclipse.

We’re just about to move one of our workstations to an AMD64, and would like to know if there are any other known problems with Eclipse, particularly in combination with MyEclipse.

[cjohan]

The X86_64 version of Eclipse in SUSE Linux 9.2 has some UI problems that cause JVM crashes and they have nothing to do wit MyEclipse. Before even installing MyEclipse, expanding a folder to see which files are in it and opening a file occasionally cause such a crash. Some very simple apps, such as HelloWorld, seem fine — no UI problems. Maybe there is some Java syntax feature that triggers the crash or possibly deep folder hierarchy. The Eclipse native SWT code likely is a source of that kind of problem, perhaps in combination with KDE. That is, probably only native code can crash the JVM. Possibly, the Motif version is more stable. Haven’t tried it with this version of Linux, but in Mandrake Linux 9, the Motif version was more stable than the KDE version.

[arjan.tijms]

Interesting. We have now migrated one workstation to the AMD64 platform and are working with Eclipse/MyEclipse. The OS is Debian Linux for AMD64 (only available as unstable).

So far we have indeed seen one VM crash. This might just be coicendence, as sometimes I also get this on other machines (although this is rare, maybe once or twice a year). I don’t know if this is MyEclipse related, or that it effects MyEclipse, but the message we got was:

An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x0000002a9a2b1399, pid=14176, tid=1121700208
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_01-b08 mixed mode)
# Problematic frame:
# J org.eclipse.jdt.internal.compiler.parser.Scanner.getCurrentIdentifierSource()[C
#
# An error report file with more information is saved as hs_err_pid14176.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp

There is a revision of Eclipse 3.01 comming up. Maybe it will be fixed there?

[dsarris]

I try to work in amd64 with Fedora Core 3 and sometimes I have the following error:

# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x0000002a995263c8, pid=15520, tid=1092401504
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_01-b08 mixed mode)
# Problematic frame:
# J org.eclipse.jdt.internal.compiler.parser.Scanner.getNextToken()I
#

————— T H R E A D —————
————— S Y S T E M —————

OS:Fedora Core release 3 (Heidelberg)

uname:Linux 2.6.10-1.770_FC3 #1 Thu Feb 24 18:09:38 EST 2005 x86_64
libc:glibc 2.3.4 NPTL 2.3.4
rlimit: STACK 10240k, CORE 0k, NPROC 4091, NOFILE 1024, AS infinity
load average:0.61 0.30 0.21

CPU:total 1 amd64 3dnow

Memory: 4k page, physical 508876k(20928k free), swap 1015800k(966652k free)

vm_info: Java HotSpot(TM) 64-Bit Server VM (1.5.0_01-b08) for linux-amd64, built on Dec 6 2004 20:19:46 by java_re with gcc 3.2.2 (SuSE Linux)

Does anyone have any success in using similar configuration??

thx,
tralas

[arjan.tijms]

We now get the same dreaded error about the getNextToken() more often. Using Debian GNU/Linux (unstable) it seemed to be related to apt-get updates, although that didn’t really make any sense.

Looking in the Eclipse Bugzilla DB, we encounter the following entry:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=71987

These are reports about exactly this issue. Basically it’s a VM bug and turning of JIT (slow!) or switching to IBMs VM helps.

[arjan.tijms]

Some more information for those interested:

After the update to 3.02, the MyEclipse deploy dialog on an AMD64 doesn’t work. This is caused due to an unsatisfied link in a native SWT library. MyEclipse is hit by this, and some dialogs in base Eclipse. I assume the 3.02 update will be fixed for this later, but for now a seperated patch needs to be downloaded.

After applying it, MyEclipse (and the rest of Eclipse) works as expected again.

Read about this at:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=89911

[Author]

Posts