In my opinion the most answers here regarding different architectures of Eclipse and Java are simply wrong and this can be easily checked using e.g. Process Monitor under Windows. The -vm option is there to run a specific version of java and the point of it is, that the configured process is started and runs all the Java code on its own, that's why you configure up to java.exe. In that case you DON'T need to have the same architecture for Eclipse and Java, but can happily mix both 32 Bit and 64 Bit. You only CAN'T mix both, if you DON'T use -vm, but let Eclipse load Java natively into its own process using jvm.dll and such. That latter behavior is Eclipse's default, but not the case anymore if you properly configure -vm in eclipse.ini.

如果你不相信我，你可以自己用Eclipse和Java的不同体系结构做一些测试，并正确地配置-vm。最后，这正是提问者在对公认答案的评论中所描述的:

不能运行Eclipse;JVM终止。退出代码= 13

他说64位JDK现在正在工作，但在他的截图中可以看到他的Eclipse是32位的，因为启动器的路径。库是32位的。

And now for the reason I came here: Ony of my customers had some problems loading one of our Eclipse/OSGI based applications as well and Java exited with exit code 13. In the end it showed that the problem was not about -vm or the architectures of Java and eclipse.exe, but instead he was simply missing config.ini and I guess eclipse.exe wasn't aware what to load or such. After we recognized that and put a config.iniback in place, the app loaded fine with using -vm and a 64 Bit JRE7 in combination with a 32 Bit eclipse.exe.

确保您使用的Eclipse和Java都是32位或64位的。

不能在32位JRE下运行64位eclipse。

java -version

Java HotSpot(TM) 64位服务器虚拟机

32位版本的JRE没有64位。

使用下面的配置;

    -startup
    plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
    --launcher.library
    plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20130807-1835
    -product
    org.springsource.ggts.ide
    --launcher.defaultAction
    openFile
    --launcher.XXMaxPermSize
    256M
    -vm
    C:\Program Files\Java\jdk1.7.0_51\jre\bin\javaw.exe
    -vmargs
    -Dorg.eclipse.swt.browser.IEVersion=10001
    -Dgrails.console.enable.interactive=false
    -Dgrails.console.enable.terminal=false
    -Djline.terminal=jline.UnsupportedTerminal
    -Dgrails.console.class=grails.build.logging.GrailsEclipseConsole
    -Dosgi.requiredJavaVersion=1.6
    -Xms40m
    -Xmx768m
    -XX:MaxPermSize=256m
    -Dorg.eclipse.swt.browser.IEVersion=10001

使用Eclipse Neon的人

我想运行Eclipse Neon, JRE 1.8但是JDK 1.7 返回error=13 然后我安装了java JDK 1.8，一切都很顺利

我也有这个问题。我有一个旧的JDK1.8.0_05。我安装了最新的JDK1.8.0_111，现在一切都很好。一定要更新环境变量。

我用的是64位的Windows 7。 使用Eclipse Neon 1a。

希望这能帮助到别人。

最近我也遇到了同样的问题。我的eclipse版本不支持java版本8。

我不小心在我的机器上安装了jre 8，它通过在开始时附加“C:\ProgramData\Oracle\Java\javapath”来自动更新我的PATH变量，这导致eclipse选择这个版本(并忽略手动添加的1.6版本，它是后来的顺序)，并崩溃退出代码13。

我只是从路径中删除了这个字符串，从而导致系统选择我的旧版本，eclipse开始正常。