Community
Participate
Working Groups
I get the following when trying to launch a debug session. I can open the Debug perspective ok, but going "Run", "Debug" and selecting my application results in a dialog box with the message "An internal error occurred during : "Launching"". THe following is the stacktrace from .log. I've done a quick google for that class, and searched my eclipse install for any file with that name. I can't find a thing !ENTRY org.eclipse.core.runtime 4 2 2005-01-14 20:41:39.312 !MESSAGE An internal error occurred during: "Launching". !STACK 0 java.lang.NoClassDefFoundError: org/eclipse/debug/internal/core/memory/IExtendedMemoryBlockRetrieval at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:298) at org.eclipse.core.runtime.adaptor.EclipseClassLoader.defineClass(EclipseClassLoader.java:223) at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.findClassImpl(DefaultClassLoader.java:281) at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultClassLoader.findClass(DefaultClassLoader.java:172) at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.findLocalClass(AbstractClassLoader.java:220) at org.eclipse.core.runtime.adaptor.EclipseClassLoader.basicFindLocalClass(EclipseClassLoader.java:135) at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:59) at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:371) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:402) at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:93) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315) at org.eclipse.cdt.debug.internal.core.model.CDebugTarget.<init>(CDebugTarget.java:243) at org.eclipse.cdt.debug.core.CDIDebugModel$1.run(CDIDebugModel.java:96) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1674) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1694) at org.eclipse.cdt.debug.core.CDIDebugModel.newDebugTarget(CDIDebugModel.java:107) at org.eclipse.cdt.launch.internal.LocalRunLaunchDelegate.launch(LocalRunLaunchDelegate.java:102) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:588) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:513) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:738) at org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:910) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
Are you using Eclipse 3.1 M4?
Yes. Sorry I forgot to mention it
There are some API changes in the Eclipse 3.1 M4 and it is incompatible with CDT 2.1. If we decide to release 2.1.1 we probably should fix it. But for now you can only use it with Eclipse 3.0.x.
*** Bug 83179 has been marked as a duplicate of this bug. ***
*** Bug 83510 has been marked as a duplicate of this bug. ***
*** Bug 83594 has been marked as a duplicate of this bug. ***
We have decided to remove the support of the platform's memory view to avoid this situation.
Fixed.
*** Bug 84288 has been marked as a duplicate of this bug. ***
*** Bug 84643 has been marked as a duplicate of this bug. ***
*** Bug 87125 has been marked as a duplicate of this bug. ***
*** Bug 87737 has been marked as a duplicate of this bug. ***
*** Bug 88989 has been marked as a duplicate of this bug. ***