dev-manual: Review edits for GDB without source

Fixes [YOCTO #6621]

Applied a few review edits for this fix.

(From yocto-docs rev: 99511bbcfa1de2f7bf691da1a002913f3a7f6034)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 12 insertions, 2 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 32500921aa..604c484f30 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -8250,7 +8250,7 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
         </para>
 
         <tip>
-            For best results, install DBG (<filename>-dbg</filename>) packages
+            For best results, install debug (<filename>-dbg</filename>) packages
             for the applications you are going to debug.
             Doing so makes extra debug symbols available that give you more
             meaningful output.
@@ -8280,6 +8280,15 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
             as all the heavy debugging is done by the host GDB.
             Offloading these processes gives the Gdbserver running on the target a chance to remain
             small and fast.
+            <note>
+                By default, source files are part of the
+                <filename>*-dbg</filename> packages in order to enable GDB
+                to show source lines in its output.
+                You can save further space on the target by setting the
+                <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_DEBUG_SPLIT_STYLE'><filename>PACKAGE_DEBUG_SPLIT_STYLE</filename></ulink>
+                variable to "debug-without-src" so that these packages do not
+                include the source files.
+            </note>
         </para>
 
         <para>
@@ -8995,7 +9004,8 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
             takes place.
             You can gain access to the symbols by using "dbg-pkgs" in the
             <filename>IMAGE_FEATURES</filename> variable or by
-            installing the appropriate DBG (<filename>-dbg</filename>) packages.
+            installing the appropriate debug (<filename>-dbg</filename>)
+            packages.
         </para>
 
         <para>