Community
Participate
Working Groups
Build Identifier: Eclipse Platform Version: 3.7.0 Build id: I20110613-1736 org/eclipse/cdt/dsf/gdb/launching/GdbLaunch Hi, I haven't had any luck with the debugger aspect of Eclipse. I have a simple pyDev module. Is it correct for it to still be calling cdt and GdbLaunch? I would have expected a java interpreter to be used for step-through debugging of PyDev projects. My most recent project before this was a CDT c++ project. I was unable to get debugging working for this as well. In workspace/.metadata/.log org.eclipse.debug.ui 4 120 2011-12-24 16:22:22.193 !MESSAGE Error logged from Debug UI: !STACK 0 java.lang.NoClassDefFoundError: org/eclipse/cdt/dsf/gdb/launching/GdbLaunch at org.eclipse.cdt.dsf.gdb.internal.ui.actions.ConnectActionDelegate.getConnectCommand(ConnectActionDelegate.java:76) at org.eclipse.cdt.dsf.gdb.internal.ui.actions.ConnectActionDelegate.updateEnablement(ConnectActionDelegate.java:63) at org.eclipse.cdt.dsf.gdb.internal.ui.actions.ConnectActionDelegate.debugContextChanged(ConnectActionDelegate.java:52) at org.eclipse.debug.internal.ui.contexts.DebugWindowContextService$1.run(DebugWindowContextService.java:194) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.debug.internal.ui.contexts.DebugWindowContextService.notify(DebugWindowContextService.java:192) at org.eclipse.debug.internal.ui.contexts.DebugWindowContextService.notify(DebugWindowContextService.java:181) at org.eclipse.debug.internal.ui.contexts.DebugWindowContextService.debugContextChanged(DebugWindowContextService.java:390) at org.eclipse.debug.ui.contexts.AbstractDebugContextProvider$1.run(AbstractDebugContextProvider.java:79) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.debug.ui.contexts.AbstractDebugContextProvider.fire(AbstractDebugContextProvider.java:77) at org.eclipse.debug.internal.ui.views.launch.LaunchView$ContextProviderProxy.debugContextChanged(LaunchView.java:477) at org.eclipse.debug.ui.contexts.AbstractDebugContextProvider$1.run(AbstractDebugContextProvider.java:79) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.debug.ui.contexts.AbstractDebugContextProvider.fire(AbstractDebugContextProvider.java Reproducible: Always Steps to Reproduce: 1.load a pyDev or C++ project 2. for python run the project as python run for c++ build debug version 3. launch debugger
Moving to CDT for comment.
Sounds like an installation issue. Do you have the org.eclipse.cdt.dsf.gdb plugin installed. As for python, I don't think is should be using the CDT launch. You can go to Run->Debug configurations... to see the launch that is being used by your project. Also, there may be a python launch configuration type you can choose on the left hand side.
I installed pydev 2.4 with CDT 8.0.1 and was able to debug both pydev projects and CDT projects. I also tried Adding CDT nature to a pydev project and I was able to debug both the python module and the executable. I think this is an installation issue.
Two people now feel this is a configuration issue. If there is no feedback from the person that opened the bug by mid-next week, let's close as WORKSFORME
No response, assuming it was an installation issue.
