Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DSDP - Target Management » Remote Debugging
Remote Debugging [message #1691] Thu, 09 November 2006 16:27 Go to next message
Eclipse User
Originally posted by: george.vassilakes.elekta.com

Hi,

apologies if I am not posting in the correct forum.

I am using eclipse 3.2.1 with CDT 3.1.1 and RSE SDK 1.0RC4
I am running on a windows XP and my remote target is a Linux Suse 9.3.

I can setup targets to the linux box and check the processes running there
and create shells. I can do it this with both ssh and dstore.
I can run my application on the target without problems when I hit the run
button.
The problem I have is with debugging when I launch the debugger it starts
a new process with gdbserver on the remote target and starts listening on
port 2345. see below:
----------------------------------------
sh

/home/uklvasg>
gdbserver :2345 /usr/rhp/eclipse/vision/VisionTest;exit
Process /usr/rhp/eclipse/vision/VisionTest created; pid = 15931
Listening on port 2345
/home/uklvasg>
Remote debugging from host 130.141.105.235
---------------------------------------

After 2 seconds I get an error message box saying
Target selection failed
Target is not responding (timed out)

I have tried to increase the wait time of the debugger but no difference.
I also checked that the process and gdb are running fine on the target
waiting for commands on the port 2345.

I have now run out of ideas and don't know how to get it working.
I would appreciate any help.

Thanks
George

PS. I list the .log related entries below

-----------------------------------------------------

!ENTRY org.eclipse.cdt.debug.mi.core 4 150 2006-11-09 16:26:20.316
!MESSAGE Target selection failed.
!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:601)
at org.eclipse.cdt.debug.mi.core.MISession.postCommand(MISessio n.java:567)
at
org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.startGDB ServerSession(GDBServerCDIDebugger2.java:100)
at
org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.doStartS ession(GDBServerCDIDebugger2.java:43)
at
org.eclipse.cdt.debug.mi.core.AbstractGDBCDIDebugger.createS ession(AbstractGDBCDIDebugger.java:79)
at
org.eclipse.rse.remotecdt.RemoteRunLaunchDelegate.launch(Rem oteRunLaunchDelegate.java:111)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:639)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:565)
at
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:754)
at
org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlu gin.java:944)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
!SUBENTRY 1 org.eclipse.cdt.debug.mi.core 4 150 2006-11-09 16:26:20.316
!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:601)
at org.eclipse.cdt.debug.mi.core.MISession.postCommand(MISessio n.java:567)
at
org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.startGDB ServerSession(GDBServerCDIDebugger2.java:100)
at
org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.doStartS ession(GDBServerCDIDebugger2.java:43)
at
org.eclipse.cdt.debug.mi.core.AbstractGDBCDIDebugger.createS ession(AbstractGDBCDIDebugger.java:79)
at
org.eclipse.rse.remotecdt.RemoteRunLaunchDelegate.launch(Rem oteRunLaunchDelegate.java:111)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:639)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:565)
at
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:754)
at
org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlu gin.java:944)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

!ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.676
!MESSAGE RESOURCE CHANGED EVENT: eventType=POST_CHANGE,
eventSource=org.eclipse.core.internal.resources.Workspace@1325aef

!ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.676
!MESSAGE ...In preScanForIgnore. Kind = CHANGED

!ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.691
!MESSAGE ......resource is: vision, type is: project

!ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.691
!MESSAGE ......flags == 0

!ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.707
!MESSAGE EVENT FILTERED OUT IN PRESCAN
-------------------------------------------------------
Re: Remote Debugging [message #1700 is a reply to message #1691] Fri, 10 November 2006 12:17 Go to previous messageGo to next message
Martin Oberhuber is currently offline Martin Oberhuber
Messages: 983
Registered: July 2009
Senior Member
Hi George,

could it be that a firewall prevents access to port 2345 from the
outside? - I'd recommend testing the setup with gdb on the commandline,
if you can do that:

Remote side -> gdbserver :2345 /your/app
Local side -> gdb /your/app,
then on the (gdb) prompt enter
target remote remote.host.com:2345

If this doesn't help, I'd recommend filing a bugzilla report
for further investigation, this will increase visibility and
help making answers/responses trackable.

Thanks,
--
Martin Oberhuber
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm


George wrote:
> Hi,
>
> apologies if I am not posting in the correct forum.
>
> I am using eclipse 3.2.1 with CDT 3.1.1 and RSE SDK 1.0RC4
> I am running on a windows XP and my remote target is a Linux Suse 9.3.
>
> I can setup targets to the linux box and check the processes running
> there and create shells. I can do it this with both ssh and dstore.
> I can run my application on the target without problems when I hit the
> run button. The problem I have is with debugging when I launch the
> debugger it starts a new process with gdbserver on the remote target and
> starts listening on port 2345. see below:
> ----------------------------------------
> sh
>
> /home/uklvasg>
> gdbserver :2345 /usr/rhp/eclipse/vision/VisionTest;exit
> Process /usr/rhp/eclipse/vision/VisionTest created; pid = 15931
> Listening on port 2345
> /home/uklvasg>
> Remote debugging from host 130.141.105.235
> ---------------------------------------
>
> After 2 seconds I get an error message box saying
> Target selection failed
> Target is not responding (timed out)
>
> I have tried to increase the wait time of the debugger but no
> difference. I also checked that the process and gdb are running fine on
> the target waiting for commands on the port 2345.
>
> I have now run out of ideas and don't know how to get it working.
> I would appreciate any help.
>
> Thanks
> George
>
> PS. I list the .log related entries below
>
> -----------------------------------------------------
>
> !ENTRY org.eclipse.cdt.debug.mi.core 4 150 2006-11-09 16:26:20.316
> !MESSAGE Target selection failed.
> !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:601)
> at
> org.eclipse.cdt.debug.mi.core.MISession.postCommand(MISessio n.java:567)
> at
> org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.startGDB ServerSession(GDBServerCDIDebugger2.java:100)
>
> at
> org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.doStartS ession(GDBServerCDIDebugger2.java:43)
>
> at
> org.eclipse.cdt.debug.mi.core.AbstractGDBCDIDebugger.createS ession(AbstractGDBCDIDebugger.java:79)
>
> at
> org.eclipse.rse.remotecdt.RemoteRunLaunchDelegate.launch(Rem oteRunLaunchDelegate.java:111)
>
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:639)
>
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:565)
>
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:754)
>
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlu gin.java:944)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
> !SUBENTRY 1 org.eclipse.cdt.debug.mi.core 4 150 2006-11-09 16:26:20.316
> !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:601)
> at
> org.eclipse.cdt.debug.mi.core.MISession.postCommand(MISessio n.java:567)
> at
> org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.startGDB ServerSession(GDBServerCDIDebugger2.java:100)
>
> at
> org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.doStartS ession(GDBServerCDIDebugger2.java:43)
>
> at
> org.eclipse.cdt.debug.mi.core.AbstractGDBCDIDebugger.createS ession(AbstractGDBCDIDebugger.java:79)
>
> at
> org.eclipse.rse.remotecdt.RemoteRunLaunchDelegate.launch(Rem oteRunLaunchDelegate.java:111)
>
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:639)
>
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:565)
>
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:754)
>
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlu gin.java:944)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>
> !ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.676
> !MESSAGE RESOURCE CHANGED EVENT: eventType=POST_CHANGE,
> eventSource=org.eclipse.core.internal.resources.Workspace@1325aef
>
> !ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.676
> !MESSAGE ...In preScanForIgnore. Kind = CHANGED
>
> !ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.691
> !MESSAGE ......resource is: vision, type is: project
>
> !ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.691
> !MESSAGE ......flags == 0
>
> !ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.707
> !MESSAGE EVENT FILTERED OUT IN PRESCAN
> -------------------------------------------------------
>
Re: Remote Debugging [message #2738 is a reply to message #1700] Mon, 13 November 2006 11:37 Go to previous message
Eclipse User
Originally posted by: george.vassilakes.elekta.com

Hi,

I actually have it working now. The problem was with the version of gdb I
was using not supporting cross-debugging. I downloaded and build a
cross-debugging version and now everything works fine.

Thanks for your help it was very easy to identify the problem from the
command line once I tried to run the debugger outside eclipse.
Re: Remote Debugging [message #565025 is a reply to message #1691] Fri, 10 November 2006 12:17 Go to previous message
Martin Oberhuber is currently offline Martin Oberhuber
Messages: 983
Registered: July 2009
Senior Member
Hi George,

could it be that a firewall prevents access to port 2345 from the
outside? - I'd recommend testing the setup with gdb on the commandline,
if you can do that:

Remote side -> gdbserver :2345 /your/app
Local side -> gdb /your/app,
then on the (gdb) prompt enter
target remote remote.host.com:2345

If this doesn't help, I'd recommend filing a bugzilla report
for further investigation, this will increase visibility and
help making answers/responses trackable.

Thanks,
--
Martin Oberhuber
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm


George wrote:
> Hi,
>
> apologies if I am not posting in the correct forum.
>
> I am using eclipse 3.2.1 with CDT 3.1.1 and RSE SDK 1.0RC4
> I am running on a windows XP and my remote target is a Linux Suse 9.3.
>
> I can setup targets to the linux box and check the processes running
> there and create shells. I can do it this with both ssh and dstore.
> I can run my application on the target without problems when I hit the
> run button. The problem I have is with debugging when I launch the
> debugger it starts a new process with gdbserver on the remote target and
> starts listening on port 2345. see below:
> ----------------------------------------
> sh
>
> /home/uklvasg>
> gdbserver :2345 /usr/rhp/eclipse/vision/VisionTest;exit
> Process /usr/rhp/eclipse/vision/VisionTest created; pid = 15931
> Listening on port 2345
> /home/uklvasg>
> Remote debugging from host 130.141.105.235
> ---------------------------------------
>
> After 2 seconds I get an error message box saying
> Target selection failed
> Target is not responding (timed out)
>
> I have tried to increase the wait time of the debugger but no
> difference. I also checked that the process and gdb are running fine on
> the target waiting for commands on the port 2345.
>
> I have now run out of ideas and don't know how to get it working.
> I would appreciate any help.
>
> Thanks
> George
>
> PS. I list the .log related entries below
>
> -----------------------------------------------------
>
> !ENTRY org.eclipse.cdt.debug.mi.core 4 150 2006-11-09 16:26:20.316
> !MESSAGE Target selection failed.
> !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:601)
> at
> org.eclipse.cdt.debug.mi.core.MISession.postCommand(MISessio n.java:567)
> at
> org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.startGDB ServerSession(GDBServerCDIDebugger2.java:100)
>
> at
> org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.doStartS ession(GDBServerCDIDebugger2.java:43)
>
> at
> org.eclipse.cdt.debug.mi.core.AbstractGDBCDIDebugger.createS ession(AbstractGDBCDIDebugger.java:79)
>
> at
> org.eclipse.rse.remotecdt.RemoteRunLaunchDelegate.launch(Rem oteRunLaunchDelegate.java:111)
>
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:639)
>
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:565)
>
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:754)
>
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlu gin.java:944)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
> !SUBENTRY 1 org.eclipse.cdt.debug.mi.core 4 150 2006-11-09 16:26:20.316
> !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:601)
> at
> org.eclipse.cdt.debug.mi.core.MISession.postCommand(MISessio n.java:567)
> at
> org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.startGDB ServerSession(GDBServerCDIDebugger2.java:100)
>
> at
> org.eclipse.cdt.debug.mi.core.GDBServerCDIDebugger2.doStartS ession(GDBServerCDIDebugger2.java:43)
>
> at
> org.eclipse.cdt.debug.mi.core.AbstractGDBCDIDebugger.createS ession(AbstractGDBCDIDebugger.java:79)
>
> at
> org.eclipse.rse.remotecdt.RemoteRunLaunchDelegate.launch(Rem oteRunLaunchDelegate.java:111)
>
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:639)
>
> at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfiguration.java:565)
>
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.java:754)
>
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlu gin.java:944)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>
> !ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.676
> !MESSAGE RESOURCE CHANGED EVENT: eventType=POST_CHANGE,
> eventSource=org.eclipse.core.internal.resources.Workspace@1325aef
>
> !ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.676
> !MESSAGE ...In preScanForIgnore. Kind = CHANGED
>
> !ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.691
> !MESSAGE ......resource is: vision, type is: project
>
> !ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.691
> !MESSAGE ......flags == 0
>
> !ENTRY org.eclipse.rse.ui 1 0 2006-11-09 16:26:20.707
> !MESSAGE EVENT FILTERED OUT IN PRESCAN
> -------------------------------------------------------
>
Re: Remote Debugging [message #565054 is a reply to message #1700] Mon, 13 November 2006 11:37 Go to previous message
Eclipse User
Originally posted by: george.vassilakes.elekta.com

Hi,

I actually have it working now. The problem was with the version of gdb I
was using not supporting cross-debugging. I downloaded and build a
cross-debugging version and now everything works fine.

Thanks for your help it was very easy to identify the problem from the
command line once I tried to run the debugger outside eclipse.
Previous Topic:Remote Debugging
Next Topic:RSE 1.0 is released!
Goto Forum:
  


Current Time: Tue Sep 23 06:28:12 GMT 2014

Powered by FUDForum. Page generated in 0.06506 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software