|
Re: gdb on amd64 linux not starting [message #139335 is a reply to message #139324] |
Tue, 22 February 2005 01:03 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: mikhailkhod.rogers.com
See CDT Debug FAQ #5 -"Can I see/log all of the commands which are being
driven to gdb?".
This also includes the command line that CDT executes to start gdb.
"Andrew McGhee" <andrew.mcghee@geniushealth.com> wrote in message
news:cvdv8d$fqr$1@www.eclipse.org...
> Hello,
> We are running Eclipse 3.0.1 with CDT 2.1.0
> When trying to kick start the debugger on our main method, we are getting
a
> timeout. The log file eclipseWorkspace/.metadata/.log shows the following
> stack trace
>
> !MESSAGE Target is not responding (timed out)
> !STACK 0
> org.eclipse.cdt.debug.mi.core.MIException: Target is not responding (timed
> out)
> at
> org.eclipse.cdt.debug.mi.core.MISession.postCommand0(MISessi on.java:378)
> at
> org.eclipse.cdt.debug.mi.core.MISession.postCommand(MISessio n.java:349)
> at
>
org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger.createLau nchSession(GDBSe
rverCDIDebugger.java:75)
> ...
>
>
> We are running gcc-3.3, our version of gdb is 6.1. (gdb runs fine with the
> given target from the command line)
>
> Has anyone else got gdb running within eclipse on the AMD64 based system?
>
> Are there any pointers as to how to enable debugging within the
> org.eclipse.cdt.debug.mi.core section, to try and get greater details as
to
> the exact command that CDT is trying to run?
>
> Many thanks,
>
> Andrew McGhee
>
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03384 seconds