Changes between Version 4 and Version 5 of Debugging/Newlib

Timestamp:

09/05/16 01:52:01 (8 years ago)

Author:

Gene Smith

Comment:

--

Debugging/Newlib

@@ -13 +13 @@
 }}}
 
-To make the source code available to the debugger you need to unpack the Newlib source used by the RSB and you need to tell the debugger where find it. 
+Take note of the number of `../` levels in the source path above. In this example there are six. This can vary depending on build environment.
+
+To make the source code available to the debugger you need to unpack the Newlib source used by the RSB and you need to tell the debugger where to find it. 
 
 My RSB is located at `/opt/work/chris/rtems/rsb/rtems-source-builder.git` and the source used to build the tools is under the `rtems/source` in the RSB.
@@ -29 +31 @@
 The Newlib version is `Newlib 2.4.0.20160527` so the source is `newlib-2.4.0.20160527.tar.gz`.
 
-Change directory to a location on the host machine GDB is running on and create a directory to unpack the Newlib source. Create the directory and unpack the source:
+Change directory to a convenient location on the host machine GDB is running on and create a directory to unpack the Newlib source. Create the directory and unpack the source inside it:
 
 {{{
 $ cd /opt/work/chris/rtems
 $ mkdir src
+$ cd src
 $ tar zxf /opt/work/chris/rtems/rsb/rtems-source-builder.git/rtems/sources/newlib-2.4.0.20160527.tar.gz
 }}}
@@ -46 +49 @@
 }}}
 
-Create the internal work directories GCC had when the source was built. You can see these in the path as `../../../../../..`:
+Create dummy internal work directories like GCC had when Newlib was built. This is the number of levels that were noted above that you can see in the source path as the leading series of `../` (six in this example, but this can vary depending on your build environment):
 
 {{{