Eclipse Community Forums: C / C++ IDE (CDT) » gdb on amd64 linux not starting

Help

Home

Home » Language IDEs » C / C++ IDE (CDT) » gdb on amd64 linux not starting

Show: Today's Messages :: Show Polls :: Message Navigator

gdb on amd64 linux not starting [message #139324]

Tue, 22 February 2005 00:42

Andrew McGhee

Messages: 6
Registered: July 2009

Junior Member

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(GDBServerCDIDebugger.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

Report message to a moderator

Re: gdb on amd64 linux not starting [message #139335 is a reply to message #139324]

Tue, 22 February 2005 01:03

Eclipse User

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
>
>

Report message to a moderator

Re: gdb on amd64 linux not starting [message #139344 is a reply to message #139324]

Tue, 22 February 2005 02:22

Javier Kohen

Messages: 35
Registered: July 2009

Member

Hi Andrew,

I reported this bug to CDT's bug tracking system. See the report at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=85124 and make sure you
add there all you find out :)

While you're there, please vote for the bug if you're intersted.

Cheers,

Andrew McGhee wrote:
> 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)

Report message to a moderator

Re: gdb on amd64 linux not starting [message #139353 is a reply to message #139344]

Tue, 22 February 2005 02:24

Javier Kohen

Messages: 35
Registered: July 2009

Member

Oh, well, on a careful look it's not the exact same bug, but I'm sure
it'll hit you eventually as we're using the same platform.

I'm still debugging from the command-line (GCC 3.4 and GDB 6.3) at the
moment.

Javier Kohen wrote:
>
> Hi Andrew,
>
> I reported this bug to CDT's bug tracking system. See the report at
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=85124 and make sure you
> add there all you find out :)
>
> While you're there, please vote for the bug if you're intersted.
>
> Cheers,
>
> Andrew McGhee wrote:
>
>> 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)

Report message to a moderator

Previous Topic:	stl and code assist
Next Topic:	Newbie: CDT + OSX = .exe's?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Sep 01 05:13:24 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter