Eclipse Community Forums: Newcomers » Eclipse crashes after changing -vm paths

Help

Home

Home » Newcomers » Newcomers » Eclipse crashes after changing -vm paths

Show: Today's Messages :: Show Polls :: Message Navigator

Eclipse crashes after changing -vm paths [message #1710915]

Sat, 10 October 2015 20:57

Luke Purnell

Messages: 4
Registered: October 2015

Junior Member

I am running Ubuntu 12.04 on a macbook pro (dual boot).

I had Java 1.6 installed but upgraded to java 1.7 in order to use a plug in (testNG)

When I tried to use my plugin I got an error message from Eclipse saying the vm was 1.6 and testNG required a vm of java 1.7

I then changed my eclipse.ini file to contain the following line:

-vm
{YOUR_JAVA_7_HOME}/jre/lib/server/libjvm.dylib

After I edited my eclipse.ini file to contain these two lines Eclipse crashed upon start up with the below crash report.

I then deleted these lines in the eclipse.ini file and it now reads as below. However Eclipse still crashes upon start up.

ECLIPSE.INI FILE

-startup
plugins/org.eclipse.equinox.launcher_1.2.0.dist.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.dist
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Xms40m
-Xmx384m
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/usr/share/eclipse/dropins

ECLIPSE CRASH LOG

!SESSION 2015-10-10 21:46:51.043 -----------------------------------------------
eclipse.buildId=I20110613-1736
java.version=1.7.0_80
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB
Command-line arguments: -os linux -ws gtk -arch x86_64

!ENTRY org.eclipse.osgi 4 0 2015-10-10 21:46:56.378
!MESSAGE Application error
!STACK 1
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
no swt-gtk-3740 in java.library.path
no swt-gtk in java.library.path
Can't load library: /home/luke/.swt/lib/linux/x86_64/libswt-gtk-3740.so
Can't load library: /home/luke/.swt/lib/linux/x86_64/libswt-gtk.so

at org.eclipse.swt.internal.Library.loadLibrary(Library.java:285)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:194)
at org.eclipse.swt.internal.C.<clinit>(C.java:21)
at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63)
at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54)
at org.eclipse.swt.widgets.Display.<clinit>(Display.java:132)
at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:695)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:153)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:95)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)

Report message to a moderator

Re: Eclipse crashes after changing -vm paths [message #1710922 is a reply to message #1710915]

Sun, 11 October 2015 07:38

Luke Purnell

Messages: 4
Registered: October 2015

Junior Member

I've also tried following the instructions here http://wiki.eclipse.org/Eclipse.ini where I updated my -vm path as instructed but I still get the same crash on startup.

Report message to a moderator