Hello,
I'm using EPIC 0.6.25 with Eclipse 3.4 on Windows. I've reproduced this on both Windows XP and Windows 98SE :)
Bug description:
Eclipse starts in perspective you closed it with.
If I quit Eclipse in perspective other than Debug, variables window stay empty when I start debugging later (in debug perspective). But if I quit Eclipse in Debug perspective, everything is working fine. If you have troubles reproducing this problem I'll help.
EPIC is great!
Best Regards,
Stanimir
I have the same problem with that same version of EPIC, but it only happens with Eclipse 3.4.0 and 3.4.1, and not with Eclipse 3.3
I have the same problem using EPIC 0.6.27 with Eclipse 3.4.1 on Linux.
The eclipse log reads this:
----
!ENTRY org.eclipse.debug.ui 4 120 2008-12-10 17:00:38.023
!MESSAGE Error logged from Debug UI:
!STACK 0
java.lang.ClassCastException: org.epic.debug.db.StackFrame cannot be cast to org.eclipse.jdt.debug.core.IJavaStackFrame
at org.eclipse.jdt.internal.debug.ui.EvaluationContextManager.debugContextChanged(EvaluationContextManager.java:263)
at org.eclipse.debug.internal.ui.contexts.DebugWindowContextService$1.run(DebugWindowContextService.java:169)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.debug.internal.ui.contexts.DebugWindowContextService.notify(DebugWindowContextService.java:167)
at org.eclipse.debug.internal.ui.contexts.DebugWindowContextService.notify(DebugWindowContextService.java:151)
at org.eclipse.debug.internal.ui.contexts.DebugWindowContextService.debugContextChanged(DebugWindowContextService.java:316)
at org.eclipse.debug.ui.contexts.AbstractDebugContextProvider$1.run(AbstractDebugContextProvider.java:79)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.debug.ui.contexts.AbstractDebugContextProvider.fire(AbstractDebugContextProvider.java:77)
at org.eclipse.debug.internal.ui.views.launch.LaunchView$ContextProvider.access$2(LaunchView.java:1)
at org.eclipse.debug.internal.ui.views.launch.LaunchView$1.runInUIThread(LaunchView.java:259)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3378)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3036)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
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:386)
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:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
----
It seems to me that the class hierarchy of org.eclipse.jdt.debug has changed.
Daniel Murguía.