Debugging c application on VF50 using gdb

Hi all,

I need to debug a C application with GDB on arm target(VF50). Please someone elaborate the steps needed to setup a gdb on VF50 and the debug .

Please see the gdb documentation here. gdbserver is deployed by default on our modules. On ARM target VF50, gdbserver can be run as follows

root@colibri-vf:~# gdbserver hello 
Process hello created; pid = 413
Listening on port 2345

where is the ip address of the Colibri Vybrid module and 2345 is the port number on which gdbserver will listen for connection. “hello” is the executable binary which just prints hello world.

On host, assuming you have the toolchain as per here, execute

$ arm-linux-gnueabihf-gdb
GNU gdb (Linaro_GDB-2016.11)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-unknown-linux-gnu --target=arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) target remote
Remote debugging using
warning: No executable has been specified and target does not support
determining executable automatically.  Try using the "file" command.
0x76fcfa80 in ?? ()
(gdb) help
List of classes of commands:

aliases -- Aliases of other commands
breakpoints -- Making program stop at certain points
data -- Examining data
files -- Specifying and examining files
internals -- Maintenance commands
obscure -- Obscure features
running -- Running the program
stack -- Examining the stack
status -- Status inquiries
support -- Support facilities
tracepoints -- Tracing of program execution without stopping the program
user-defined -- User-defined commands

Type "help" followed by a class name for a list of commands in that class.
Type "help all" for the list of all commands.
Type "help" followed by command name for full documentation.
Type "apropos word" to search for commands related to "word".
Command name abbreviations are allowed if unambiguous.
(gdb) continue
[Inferior 1 (process 413) exited normally]

On target, you should something like below

root@colibri-vf:~# gdbserver hello 
Process hello created; pid = 413
Listening on port 2345
Remote debugging from host
Hello world

Child exited with status 0
GDBserver exiting

For setting up breakpoints, single stepping and such refer GDB documentation.