当前位置: 首页 > 知识库问答 >
问题:

Android Eclipse无法启动。发生错误。查看日志文件

方鸿振
2023-03-14

我知道这个问题已经在StackOverflow(和其他网站)上被问过好几次了,但我找到的所有解决方案都不适合我。

正如您在标题中看到的那样,在启动Android日食时,我收到以下错误消息:

发生错误。查看日志文件

我尝试从eclipse.ini文件中删除快照文件和Vmargs指令。我还尝试用以下命令清理Eclipse:

PATH/TO/ECLIPSE-清洁

但没有结果。

我正在Windows 7上运行ADT Eclipse包。

这是我的日志文件在我尝试运行它时(反复)所说的:

!参赛作品org . eclipse . core . resources 4 2 2014-05-26 13:45:14.494!从插件调用代码时出现消息问题:“org.eclipse.core.resources”。!堆栈0 Java . lang . nullpointerexception at org . eclipse . ui . activities . workbenchactivityhelper . is filtering(workbenchactivityhelper . Java:235)at org . eclipse . ui . internal . ide . ideworkbenchactivityhelper $ 3 . resource changed(ideworkbenchactivityhelper . Java:158)at org . eclipse . core . internal . events . notification manager $ 1 . run(notification manager . Java:291)at org . eclipse . core . runtime . safe runner . run

这是我上次关闭Eclipse之前的最后一件事:

!ENTRY org.eclipse.ui.workbench 4 0 2014-05-25 21:37:47.323
!MESSAGE An unexpected exception was thrown.
!STACK 0
java.lang.NullPointerException
    at org.eclipse.ui.internal.Workbench.createWorkbenchWindow(Workbench.java:1232)
    at org.eclipse.ui.internal.Workbench.getActiveWorkbenchWindow(Workbench.java:1225)
    at org.eclipse.ui.internal.services.WorkbenchSourceProvider.updateActiveShell(WorkbenchSourceProvider.java:924)
    at org.eclipse.ui.internal.services.WorkbenchSourceProvider.getCurrentState(WorkbenchSourceProvider.java:133)
    at org.eclipse.ui.internal.services.WorkbenchSourceProvider$6.handleEvent(WorkbenchSourceProvider.java:684)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1262)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
    at org.eclipse.swt.widgets.Decorations.WM_ACTIVATE(Decorations.java:1664)
    at org.eclipse.swt.widgets.Shell.WM_ACTIVATE(Shell.java:2145)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4525)
    at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
    at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1627)
    at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2069)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
    at org.eclipse.swt.internal.win32.OS.BringWindowToTop(Native Method)
    at org.eclipse.swt.widgets.Decorations.bringToTop(Decorations.java:231)
    at org.eclipse.swt.widgets.Shell.open(Shell.java:1217)
    at org.eclipse.jface.window.Window.open(Window.java:797)
    at org.eclipse.ui.internal.statushandlers.InternalDialog.open(InternalDialog.java:327)
    at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.doAddStatusAdapter(WorkbenchStatusDialogManagerImpl.java:270)
    at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.addStatusAdapter(WorkbenchStatusDialogManagerImpl.java:197)
    at org.eclipse.ui.statushandlers.WorkbenchStatusDialogManager.addStatusAdapter(WorkbenchStatusDialogManager.java:156)
    at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.showStatusAdapter(WorkbenchErrorHandler.java:101)
    at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.handle(WorkbenchErrorHandler.java:57)
    at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handle(IDEWorkbenchErrorHandler.java:108)
    at org.eclipse.ui.internal.WorkbenchErrorHandlerProxy.handle(WorkbenchErrorHandlerProxy.java:36)
    at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189)
    at org.eclipse.ui.internal.JFaceUtil$3.show(JFaceUtil.java:70)
    at org.eclipse.jface.util.SafeRunnable.handleException(SafeRunnable.java:67)
    at org.eclipse.core.runtime.SafeRunner.handleException(SafeRunner.java:75)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:44)
    at org.eclipse.ui.internal.Workbench.fireWindowClosed(Workbench.java:948)
    at org.eclipse.ui.internal.WorkbenchWindow.fireWindowClosed(WorkbenchWindow.java:1255)
    at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:1177)
    at org.eclipse.ui.internal.WorkbenchWindow.access$14(WorkbenchWindow.java:1136)
    at org.eclipse.ui.internal.WorkbenchWindow$10.run(WorkbenchWindow.java:1197)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:1195)
    at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:1207)
    at org.eclipse.ui.internal.WorkbenchWindow$6.close(WorkbenchWindow.java:445)
    at org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer$11.shellClosed(WBWRenderer.java:580)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:98)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062)
    at org.eclipse.swt.widgets.Decorations.closeWidget(Decorations.java:309)
    at org.eclipse.swt.widgets.Decorations.WM_CLOSE(Decorations.java:1694)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4530)
    at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
    at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1627)
    at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2069)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
    at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2541)
    at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:498)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4623)
    at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
    at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1627)
    at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2069)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
    at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2541)
    at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:498)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4623)
    at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
    at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1627)
    at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2069)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
    at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2546)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3756)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
    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:353)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
!SESSION 2014-05-26 13:23:08.484 -----------------------------------------------
eclipse.buildId=v22.3.0-887826
java.version=1.7.0_51
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product com.android.ide.eclipse.adt.package.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product com.android.ide.eclipse.adt.package.product

我真的希望你们中的一些人能帮助我解决这个问题。上次我关闭Android日食时,由于内存不足,出现了一些问题。我不知道为什么会突然发生这种情况。

共有1个答案

夏俊杰
2023-03-14

当然,刚贴出问题,我已经找到解决办法了。

如果其他人遇到同样的问题,请尝试从工作区中删除以下文件夹:

C:\.. \workspace\.metadata\.plugins\org.eclipse.e4.workbench
 类似资料:
  • 好的,今天上午我要提供一个Java演示,这里我在观众面前,无法在没有“明显”错误的情况下加载Eclipse,以人道的方式快速修复它,而不需要在论坛上爬行和经历整个调试过程。 如果有人知道我如何上传整个错误日志文件,让我知道,因为它仍然适用于页面。 我在网上搜索,可能的罪魁祸首似乎是如此之多,所以我尝试了另一个SOS在这里(每一个案例似乎都是用户特定的) 任何关于如何解决这个问题的帮助或暗示都是非常

  • 本文档介绍如何查看 TiDB 集群各组件日志,以及 TiDB 慢查询日志。 TiDB 集群各组件日志 通过 TiDB Operator 部署的 TiDB 各组件默认将日志输出在容器的 stdout 和 stderr 中。可以通过下面的方法查看单个 Pod 的日志: kubectl logs -n ${namespace} ${pod_name} 如果这个 Pod 由多个 Container 组成,

  • 我在windows上安装了ELK stack,并将Logstash配置为读取Apache日志文件。我似乎看不到Elasticsearch的输出。我对麋鹿很陌生。 环境设置 Elasticsearch:http://localhost:9200/ Logstash: Kibana:http://localhost:5601/ 以上三个应用程序都是作为服务运行的。 我创建了一个名为“logstash.

  • 问题内容: 我刚刚从http://www.eu.apache.org/dist/lucene/solr/5.3.1/solr-5.3.1.tgz下载了最新版本的Solr 。 然后我用cd /solr-5.3.1/bin将其解压缩到/ bin /目录中,以使用 根据教程和自述文件,首次试用不需要更多。 等待长达30秒才能看到Solr在端口8983上运行 [-] 30秒后仍看不到Solr在8983上收

  • 问题内容: 有没有办法像在开发中一样查看生产环境中从Rails生成的所有查询? 问题答案: 是的你可以。如果进入config / environments / production.rb文件,则有类似以下内容的部分: 取消注释config.log_level行,您将在生产中获得与在开发中相同的日志。