Now a passable Ada manual

1 files changed, 53 insertions, 15 deletions

diff --git a/doc/started_ada/gdb.t b/doc/started_ada/gdb.t
index 7ae7c2d9cd..d8820906ac 100644
--- a/doc/started_ada/gdb.t
+++ b/doc/started_ada/gdb.t
@@ -20,7 +20,7 @@ successfully used with RTEMS applications:
 Other configurations of gdb have successfully been used by RTEMS users
 but are not documented here.
 
-@section Unarchive the gdb distribution
+@section Unarchive the gdb Distribution
 
 Use the following commands to unarchive the gdb distribution:
 
@@ -31,8 +31,50 @@ tar xzf ../arc/@value{GDB-TAR}
 
 The directory @value{GDB-UNTAR} is created under the tools directory.
 
+@c 
+@c  GDB GNAT Patch
 @c
-@c  GDB Patch
+
+@section Apply GNAT Patch to GDB
+
+@ifclear GDB-GNATPATCH 
+No GNAT specific patches are required for @value{GDB-VERSION} to
+support @value{RTEMS-VERSION} and @value{GNAT-VERSION}.
+@end ifclear
+
+@ifset GDB-GNATPATCH
+
+Apply the patch using the following command sequence:
+
+@example
+cd tools/@value{GDB-UNTAR}
+zcat arc/@value{GDB-GNATPATCH} | patch -p1
+@end example
+
+Check to see if any of these patches have been rejected using the following
+sequence:
+
+@example
+cd tools/@value{GDB-UNTAR}
+find . -name "*.rej" -print
+@end example
+
+If any files are found with the .rej extension, a patch has been rejected.
+This should not happen with a good patch file.
+
+To see the files that have been modified use the sequence:
+
+@example
+cd tools/@value{GDB-UNTAR}
+find . -name "*.orig" -print
+@end example
+
+The files that are found, have been modified by the patch file.
+
+@end ifset
+
+@c
+@c  GDB RTEMS Patch
 @c
 
 @section Apply RTEMS Patch to GDB
@@ -76,7 +118,7 @@ The files that are found, have been modified by the patch file.
 
 @section GDB with Sparc Instruction Simulation (SIS)
 
-@subheading Make the build directory
+@subheading Make the Build Directory
 
 Create a build directory for the SIS Debugger
 
@@ -85,7 +127,7 @@ cd tools
 mkdir build-sis
 @end example
 
-@subheading Configure for the build
+@subheading Configure for the Build
 
 Configure the GNU Debugger for the
 Sparc Instruction Simulator (SIS):
@@ -102,7 +144,7 @@ cd tools/build-sis
 Where <INSTALL_POINT_FOR_SIS> is a unique location where the gdb
 with SIS will be created. 
 
-@subheading Make the debugger
+@subheading Make the Debugger
 
 From tools/build-sis execute the following command sequence:
 
@@ -113,7 +155,7 @@ gmake all install
 
 @section GDB with PowerPC Instruction Simulator
 
-@subheading Make the build directory
+@subheading Make the Build Directory
 
 Create a build directory for the SIS Debugger
 
@@ -122,7 +164,7 @@ cd tools
 mkdir build-ppc
 @end example
 
-@subheading Configure for the build
+@subheading Configure for the Build
 
 Configure the GNU Debugger for the PowerPC
 Instruction Simulator (PSIM):
@@ -144,7 +186,7 @@ Where <INSTALL_POINT_FOR_PPC> is a unique location where the gdb
 with PSIM will be created. 
 
 
-@subheading Make the debugger
+@subheading Make the Debugger
 
 From tools/build-ppc execute the following command sequence:
 
@@ -155,11 +197,7 @@ gmake all install
 
 @section GDB for DINK32
 
-@subheading Unarchive the gdb distribution
-
-Use the following commands to unarchive the gdb distribution:
-
-@subheading Make the build directory
+@subheading Make the Build Directory
 
 Create a build directory for the DINK32 Debugger
 
@@ -168,7 +206,7 @@ cd tools
 mkdir build-dink32
 @end example
 
-@subheading Configure for the build
+@subheading Configure for the Build
 
 Configure the GNU Debugger to communicate with
 the DINK32 ROM monitor:
@@ -184,7 +222,7 @@ cd tools/build-dink32
 Where <INSTALL_POINT_FOR_DINK32> is a unique location where the
 gdb Dink32 will be created. 
 
-@subheading Make the debugger
+@subheading Make the Debugger
 
 From tools/build-dink32 execute the following command sequence: