Aladdin - Scala Bugtracking
[#822] project: eclipse-plugin priority: medium category: bug
submitter assigned to status date submitted
Iulian Sean _ 2006-11-15 18:22:49.0
subject non-existent Scala file prevents eclipse from starting
code 
Eclipse can't start at all! Apparently, it crashes because a file which was open in the workspace does not exist anymore, and the compiler fails an assertion. Somehow this makes Eclipse think nothing works, and just exits. With no way to get it working again.

Probably this bug is just an effect of a different cause, since the path it checks is clearly wrong (I didn't delete any file).
what happened 
!ENTRY org.eclipse.osgi 4 0 2006-11-15 18:13:40.146
!MESSAGE Application error
!STACK 1
java.lang.AssertionError: assertion failed: non-existent file: /home/dragos/www/trunk/teaching/type-systems/exer\
cises/1-arithmetic/solution/solution/src/arithmetic/ArithmeticParser.scala
        at scala.Predef$.assert(Predef.scala:100)
        at scala.tools.nsc.io.PlainFile.(PlainFile.scala:31)
        at ch.epfl.lamp.sdt.ui.scalaeditor.ScalaEditor.path(ScalaEditor.java:138)
        at ch.epfl.lamp.sdt.ui.scalaeditor.ScalaEditor.tokens(ScalaEditor.java:145)
        at ch.epfl.lamp.sdt.ui.actions.AbstractSearchAction.token(AbstractSearchAction.java:30)
        at ch.epfl.lamp.sdt.ui.actions.AbstractSearchAction.update(AbstractSearchAction.java:51)
        at org.eclipse.ui.texteditor.TextEditorAction.(TextEditorAction.java:49)
        at ch.epfl.lamp.sdt.ui.actions.AbstractSearchAction.(AbstractSearchAction.java:25)
        at ch.epfl.lamp.sdt.ui.actions.SearchUses.(SearchUses.java:27)
        at ch.epfl.lamp.sdt.ui.scalaeditor.ScalaEditor.createActions(ScalaEditor.java:83)
        at org.eclipse.ui.texteditor.AbstractTextEditor.createPartControl(AbstractTextEditor.java:2682)
        at org.eclipse.ui.texteditor.StatusTextEditor.createPartControl(StatusTextEditor.java:53)
        at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.createPartControl(AbstractDecoratedTextEditor.j\
ava:367)
        at ch.epfl.lamp.sdt.ui.scalaeditor.ScalaEditor.createPartControl(ScalaEditor.java:255)
        at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
        at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
        at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
        at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
        at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140)
        at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:26\
8)
        at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
        at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation\
.java:394)
        at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144)
        at org.eclipse.ui.internal.PartStack.handleDeferredEvents(PartStack.java:1112)
        at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.java:400)
        at org.eclipse.ui.internal.PartSashContainer.handleDeferredEvents(PartSashContainer.java:1369)
        at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.java:400)
        at org.eclipse.ui.internal.WorkbenchPage.handleDeferredEvents(WorkbenchPage.java:1305)
        at org.eclipse.ui.internal.WorkbenchPage.deferUpdates(WorkbenchPage.java:1295)
        at org.eclipse.ui.internal.WorkbenchPage.restoreState(WorkbenchPage.java:2967)
        at org.eclipse.ui.internal.WorkbenchWindow.restoreState(WorkbenchWindow.java:1936)
        at org.eclipse.ui.internal.Workbench.doRestoreState(Workbench.java:2857)
        at org.eclipse.ui.internal.Workbench.access$14(Workbench.java:2805)
        at org.eclipse.ui.internal.Workbench$19.run(Workbench.java:1681)
...
what expected Scala compiler crashes should not crash Eclipse.
[back to overview]
Changes of this bug report
Iulian  edited on  2006-11-15 18:23:00.0
Sean  edited on  2006-11-16 14:12:36.0
Oops, looks like I forgot to catch/log an NSC exception somewhere. I'll add that. Note that doing CLI development in an Eclipse workspace is really dangerous, as the workspace becomes out of synch with the file system, and lots of fun crashes will occur. To get out of it, you can -rm -rf workspace/.metadata