After installing eclipse-sdk-3.0.0_pre8-r3, the first launch results in a crash (this always occurs when the ".eclipse" directory is not present) Reproducible: Always Steps to Reproduce: 1. rm -rf ~/.eclipse 2. eclipse-3 3. Actual Results: Eclipse crashes Expected Results: Eclipse should start I'm using blackdown-jdk 1.4.1 The error does not occur for the second launch (at this point the .eclipse dir exist). Removing the .eclipse directory triggers the crash again. The window that appears at the crash says: "JVM terminated. Exit code=1 /opt/blackdown-jdk-1.4.1/bin/java -cp /usr/lib/eclipse-3/startup.jar org.eclipse.core.launcher.Main -os linux -ws gtk -arch x86 -showsplash /usr/lib/eclipse-3/eclipse-gtk -showsplash 600 -exitdata /usr/lib/eclipse-3/eclipse-gtk -exitdata 4b00000a -vm /opt/blackdown-jdk-1.4.1/bin/java -vmargs -cp /usr/lib/eclipse-3/startup.jar org.eclipse.core.launcher.Main" The terminal has the additional dump that I attach.
Created attachment 32205 [details] error log of eclipse crash This is the log dumped by eclipse when it crashes.
I cannot reproduce this. I have compiled my eclipse-sdk-3.0.0_pre8-r3 with both blackdown-jdk and sun-jdk, and I have run it on blackdown-jdk irrespective of which VM was used, but I cannot reproduce your problem. I did see similar behaviour with M9, though, but that was a result of insufficient disk space at compilation time, which was not caught by the eclipse build process. I need to know 1) which VM you used to compile eclipse with 2) which USE flags did you have 3) did you compile with jikes
I did a few more tests (every time with no .eclipse, simulating the first start): - compile M8 and run M8 with blackdown 1.4.1 -> crashes - compile M9 and run M9 with blackdown 1.4.1 -> crashes (to finish compilation, I had to kill the javadoc process after a while) - compile M9 with sun 1.4.2 and run with blackdown 1.4.1 -> crashes - compile M9 and run M9 with sun -> works My USE flags: dev-util/eclipse-sdk-3.0.0_pre9 +gnome +gtk -jikes -kde -motif -mozilla I did not use jikes
Created attachment 36596 [details] modified launcher I encountered this same bug and did some research on the net. The bug is not an eclipse bug. It happens when Java loads the wrong zip library. Look at the top of the attachment provided by Alan in "Additional comment #1" below. The workaround for this is to force the correct library usage. I did this by modifying /usr/bin/eclipse-2, following a (slightly adapted) recipe from a debian forum. Look at the bottom of the attached file. It might be better to derive JAVA_HOME from the location of the Java binary, but I'm not a true shell script hacker.
