From 1ae6f9d89e2aab93255434f1399d52e341e16ecd Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 10 Apr 2013 10:56:16 -0700 Subject: [PATCH] dev-manual: Edits to remote GDB debugging section. Fixes YOCTO #3540 Further minor edits to make the example consistent. (From yocto-docs rev: 863a955f5cf119a38db4950101270bd5a53da027) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-common-tasks.xml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index c509d12c54..db12ca518d 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -3900,13 +3900,13 @@ As an example, to launch Gdbserver on the target and make it - ready to "debug" a program located in the - /usr/bin/hello directory, from the host + ready to "debug" a binary named + helloworld, from the host you need to enter a command like the following. This command connects to the target and launches Gdbserver on the target: - $ gdbserver localhost:2345 /usr/bin/hello + $ gdbserver localhost:2345 /usr/bin/helloworld Gdbserver should now be listening on port 2345 for debugging commands coming from a remote GDB process that is running on @@ -4005,12 +4005,12 @@ Finally, switch to the directory where the binary resides and run the cross-gdb binary. Provide the binary file you are going to debug. - For example, the following command form continues with the - example used in the previous section. - This command form loads the helloworld - binary as well as the debugging information: + For example, the following command continues with the + example used in the previous section by loading + the helloworld binary as well as the + debugging information: - $ i586-poky-linux-gdb helloworld + $ arm-poky-linux-gnuabi-gdb helloworld The commands in your .gdbinit execute and the GDB prompt appears.