|
| Re: Failed launching CDI Debugger [message #51933 is a reply to message #51907] |
Mon, 25 November 2002 19:18   |
Eclipse User |
|
|
|
Originally posted by: ihutchinson.providencesoftware.com
I am using Eclipse 2.0.2 with the nightly build and debugging works
fine. My configuration is Linux/2.4.x kernel/glibc 2.2.5. I use the gtk
based versions. All my settings are default including the debugger time
out info under Window->Prefernces->C\C++->Debug->GDB MI, which is set to
10000.
what is your configuration?
Ed Hintz wrote:
> I get the following error when I try to debug with the release 1.0
> 11/14/2002 build of the CDT:
>
> Failed Launching CDI Debugger: Error initializing: Timedout
>
> org.eclipse.cdt.debug.core.cdi.CDIException: Error initializing: Timedout
> at
> org.eclipse.cdt.debug.mi.core.GDBDebugger.createLaunchSessio n(GDBDebugger.java:49)
> at
> org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDel egate.launch(LocalCLaunchConfigurationDelegate.java:80)
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:136)
> at
> org.eclipse.debug.internal.ui.launchConfigurations.LaunchCon figurationDialog$10.run(LaunchConfigurationDialog.java:2299)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
>
> I can debug outside of Eclipse just fine (even using another tool that
> uses the gdb's machine interface).
>
> This is the first time trying to debug using the CDT.
>
>
>
|
|
|
| Re: Failed launching CDI Debugger [message #51959 is a reply to message #51933] |
Mon, 25 November 2002 19:41 |
| Eclipse User |
|
|
|
Originally posted by: thingsforsale.nc.rr.com
I found the problem, I had the default cygwin gdb instead of the required
5.2 in my path.
Thanks for your willingness to help.
Ed
"Iran Q. Hutchinson" <ihutchinson@providencesoftware.com> wrote in message
news:artt3q$6g5$1@rogue.oti.com...
> I am using Eclipse 2.0.2 with the nightly build and debugging works
> fine. My configuration is Linux/2.4.x kernel/glibc 2.2.5. I use the gtk
> based versions. All my settings are default including the debugger time
> out info under Window->Prefernces->C\C++->Debug->GDB MI, which is set to
> 10000.
>
> what is your configuration?
>
> Ed Hintz wrote:
> > I get the following error when I try to debug with the release 1.0
> > 11/14/2002 build of the CDT:
> >
> > Failed Launching CDI Debugger: Error initializing: Timedout
> >
> > org.eclipse.cdt.debug.core.cdi.CDIException: Error initializing:
Timedout
> > at
> >
org.eclipse.cdt.debug.mi.core.GDBDebugger.createLaunchSessio n(GDBDebugger.ja
va:49)
> > at
> >
org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDel egate.launch(Loc
alCLaunchConfigurationDelegate.java:80)
> > at
> >
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfigurati
on.java:136)
> > at
> >
org.eclipse.debug.internal.ui.launchConfigurations.LaunchCon figurationDialog
$10.run(LaunchConfigurationDialog.java:2299)
> > at
> >
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext
..java:98)
> >
> > I can debug outside of Eclipse just fine (even using another tool that
> > uses the gdb's machine interface).
> >
> > This is the first time trying to debug using the CDT.
> >
> >
> >
>
|
|
|
Powered by
FUDForum. Page generated in 0.02874 seconds
] 
Search
Help
Register
Login
Home
