[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[dsdp-tm-dev] Re: remote debugging - Windows/Unix

Hello Johanna,

I think you'll need to debug this.

Just put a breakpoint in
   REmoteRunLaunchDelegate.remoteShellExec()
and step through it from that point on.

Problem might be that the "gdbserver" program cannot
be started on the remote machine, because it is not
installed or not found by the PATH. Or, the default
port of gdbserver is already in use. Or, firewall
forbids connecting to the gdbserver port.

Also note that you need a local CROSS gdb! That is,
a version of gdb on Windows that's capable of
debugging Linux apps. You'll probably need to compile
such a gdb yourself, since I'm not aware of any
out-of-the-box open source cross toolkit -- some
commercial vendors provide it though. See also
http://dev.eclipse.org/mhonarc/lists/dsdp-tm-dev/msg00831.html

I'd recommend setting up the remote debug scenario
Linux X Linux first, then you don't need the cross
gdb. You can also set it up by hand once:
  * Log in to remote box
  * launch gdbserver manually on the remote
  * launch gdb <programname>

For a great summary of Eclipse / CDT remote development, see
http://dev.eclipse.org/mhonarc/lists/dsdp-tm-dev/msg01369.html

It has some good pointers, especially this one for a different
setup where the gdb exectuable itself runs on the remote:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=30094#c13

Yet a different approach might be possible through the
gdb implementation of the Eclipse Device Debugging Project,
http://wiki.eclipse.org/DSDP/DD/GDB

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


Johanna wrote:
sorry, we meant "C/C++ remote application" and not "remote connection"

//Johanna