remote debugging

Leon Pollak leonp at plris.com
Sun May 1 13:35:31 UTC 2011


On Sunday May 1 2011, Mahmood Naderan wrote:
> > while the "kdevelop" side connects to the target usng "target remote"
> > protocol
> >From which menu?
There is no such a menu. You need to write set of commands in your .gdbinit 
file.
Mine looks like following:
shell cp /Projects/CSU/BuildARM/debug/csu /opt/FS_DVRM/home/csu
set remote exec-file /home/csu
file /Projects/CSU/BuildARM/debug/csu
target extended-remote 192.168.50.4:44000
br main
r
-----
Comments:
Line1: copies the copmiled executable from my machine to the target machine, 
which file system is mounted in as NFS.
Line2: Defines the executable for gdbserver on the target machine.
Line3: Defines the ELF file for the gdb to look for names, lines, sorce code, 
etc...
Line4: defines for the gdb to connect to the remote machine for debugging. At 
this moment the gdbserver must be running.
Line5
-- 
Leon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop/attachments/20110501/4858d416/attachment-0001.html>


More information about the KDevelop mailing list