From d2ebf82fe7761e7adfa123dc450dc212f76d6507 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 16 Apr 2013 11:36:44 -0700 Subject: [PATCH] dev-manual: Edits to "Debugging With the Gnu Project Debugger (GDB) Remotely" section. (From yocto-docs rev: 7946fc90e83f7b40752619d408325e9c76071b5a) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 5bcf947fab..a63a13b4a0 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -4004,17 +4004,18 @@ GDB allows you to examine running programs, which in turn helps you to understand and fix problems. It also allows you to perform post-mortem style analysis of program crashes. - GDB is available as a package within the Yocto Project and by default is - installed in SDK images. + GDB is available as a package within the Yocto Project and is + installed in SDK images by default. See the "Images" chapter in the Yocto Project Reference Manual for a description of these images. You can find information on GDB at . - For best results, install -dbg packages for the applications - you are going to debug. - Doing so makes available extra debug symbols that give you more meaningful output. + For best results, install -dbg packages for + the applications you are going to debug. + Doing so makes extra debug symbols available that give you more + meaningful output.