Problem using eclipse 3.1M4 with sablevm

Hi,

Before I talk about my problem, I want to say "whow!" to thedevelopers
for this fine free java solution. I am very impressed what is functional
now in SableVM ... even such a big boy as eclipse running! Great!

Ok, now to my glitches with running eclipse with sablevm.

There are two things:

1. Starting eclipse with the script from the Wiki I got following
output:

flohr@troll:~/.bin$ ./eclipse-sablevm
!SESSION 2005-01-13 08:49:33.759
-----------------------------------------------
eclipse.buildId=I20041216-2000
java.version=?
java.vendor=?
BootLoader constants: OS=linux, ARCH=?, WS=gtk, NL=en
Command-line arguments:  -os linux -ws gtk -consolelog

!ENTRY org.eclipse.osgi 2005-01-13 08:49:33.857
!MESSAGE While loading class "org.eclipse.ui.plugin.AbstractUIPlugin",
thread "F ramework Event Dispatcher" timed out waiting (5000ms) for
thread "Main-1" to fin ish starting bundle "org.eclipse.ui.workbench".
To avoid deadlock, thread "Frame work Event Dispatcher" is proceeding
but "org.eclipse.ui.plugin.AbstractUIPlugin " may not be fully
initialized.
!STACK 0
java.lang.Exception: Generated exception.
   at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass
(Eclips eClassLoader.java:102)
   at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass
(Bund leLoader.java:371)
   at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass
(BundleLoa der.java:402)
   at
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass
(Abs tractClassLoader.java:93)
   at java.lang.ClassLoader.loadClass (ClassLoader.java:303)
   at java.lang.VirtualMachine.createClass (VirtualMachine.java:100)
   at org.eclipse.ui.plugin.AbstractUIPlugin$2.bundleChanged
(AbstractUIPlugin.j ava:585)
   at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent
( BundleContextImpl.java:1151)
   at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent
(EventManag er.java:186)
   at org.eclipse.osgi.framework.eventmgr.EventThread.run
(EventThread.java:104)
   at java.lang.VMThread.callRun (VMThread.java:120)
   at java.lang.Thread.callRun (Thread.java:391)
   at java.lang.VirtualMachine.runThread (VirtualMachine.java:121)


After a few seconds eclipse shows its workbench and all seems ok so far.


2. I opened the preferences and went to "Java/Installed JREs". The
accordant settings screen opened and showed me the former used Sun JDK.
Now I wanted to add another (sable you will have guessed) VM and pushed
the "Add" button ... that's it for eclipse:( ... eating all of my
processor time and never coming back.

There were no additional exceptions in the log or on the console.

Perhaps it is important to know that it is a completely new eclipse
installation. Unpacked the eclipse archive, then one time started it
with Sun JDK 1.4.2_06.


About my System:

AMD AthlonXP 1900
Debian Sarge (Debian Testing)
SableVM 1.1.8 (Debian Unstable)
libxalan2 2.6.0-1 (Debian Testing)
libxerces2 2.6.2-1 (Debian Testing)


Maybe this information helps!

Regards, Sascha Flohr.