Difference between revisions of "GDB"
m (→Debugging directly on target) |
|||
| Line 26: | Line 26: | ||
To debug a Core dump: | To debug a Core dump: | ||
# /mnt/host/gdb your_prog -c your_core | # /mnt/host/gdb your_prog -c your_core | ||
| − | |||
<br>[[Image:FrenchFlag.png]][[Fr:GDB| Cette page en français]] | <br>[[Image:FrenchFlag.png]][[Fr:GDB| Cette page en français]] | ||
| + | |||
| + | [[Category:Software:Debug]] | ||
Revision as of 21:26, 28 March 2008
On this page you will find all you need to debug your applications running on your Armadeus board
First of all, be sure to have installed the Toolchain During Cross Compiler configuration be sure to have choosen GDB for the Host and GDBserver options
Debugging on target from Host through Ethernet
On target launch your program like that:
# gdbserver 192.168.0.2:2345 program
192.168.0.2 is the IP address of your Host and 2345 the port number to use
On your host launch:
$ arm-linux-gdb program (gdb) target remote 192.168.0.3:2345
192.168.0.3 is the address of your target
only continue (c) can be used to start program as it is always running when you launch GDB on your host
Core dump analysis doesn't seem to work in this use case !!
Debugging directly on target
You have to build gdb for the target and have a working NFS link between your target and your host.
On target launch GDB from your NFS mount like you do it usually:
# /mnt/host/gdb your_prog
If you need argument passing:
# /mnt/host/gdb --args your_prog your_args
To debug a Core dump:
# /mnt/host/gdb your_prog -c your_core
