Community
Participate
Working Groups
When creating a new java project based on an existing directory structure, the blackdown-jdk-1.4.2_rc1/bin/java systematically terminates with the message below, while creating a fresh java project in new directory structure seems to work. VM terminated. Exit code=1 /opt/blackdown-jdk-1.4.2_rc1/bin/java -Xmx512M -verbose -cp /home/hansvw/system/eclipse/v3.0M9/./startup.jar org.eclipse.core.launcher.Main -os linux -ws gtk -arch amd64 -showsplash /home/hansvw/system/eclipse/v3.0M9/./eclipse -showsplash 600 -exitdata /home/hansvw/system/eclipse/v3.0M9/./eclipse -exitdata 13e000b -vm /opt/blackdown-jdk-1.4.2_rc1/bin/java -vmargs -Xmx512M -verbose -cp /home/hansvw/system/eclipse/v3.0M9/./startup.jar org.eclipse.core.launcher.Main The information contained in console when launching with '-verbose' vm argument: [Loaded org.eclipse.jdt.internal.compiler.ast.JavadocAllocationExpression] [Loaded org.eclipse.jface.viewers.LabelProviderChangedEvent] [Loaded org.eclipse.ui.internal.decorators.DecoratorManager$1] [Loaded org.eclipse.ui.internal.decorators.DecoratorOverlayIcon] [Loaded org.eclipse.swt.internal.gtk.GdkImage]
Looks like a VM bug. Is there VM dump or trace file?
Closing. Please re-open if you have a VM log and can provide us with more info. Thanks.