diff options
Diffstat (limited to 'doc/started/gdb.t')
| -rw-r--r-- | doc/started/gdb.t | 222 |
1 files changed, 0 insertions, 222 deletions
diff --git a/doc/started/gdb.t b/doc/started/gdb.t deleted file mode 100644 index 13716ca635..0000000000 --- a/doc/started/gdb.t +++ /dev/null @@ -1,222 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1998. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Building the GNU Debugger - -GDB is not currently RTEMS aware. The following configurations have been -successfully used with RTEMS applications: - -@itemize @bullet -@item Sparc Instruction Simulator (SIS) -@item PowerPC Instruction Simulator (PSIM) -@item DINK32 -@end itemize - -Other configurations of gdb have successfully been used by RTEMS users -but are not documented here. - -@section Unarchive the gdb Distribution - -Use the following commands to unarchive the gdb distribution: - -@example -cd tools -tar xzf ../archive/@value{GDB-TAR} -@end example - -The directory @value{GDB-UNTAR} is created under the tools directory. - -@c -@c GDB Patch -@c - -@section Apply RTEMS Patch to GDB - -@ifclear GDB-RTEMSPATCH -No RTEMS specific patches are required for @value{GDB-VERSION} to -support @value{RTEMS-VERSION}. -@end ifclear - -@ifset GDB-RTEMSPATCH - -Apply the patch using the following command sequence: - -@example -cd tools/@value{GDB-UNTAR} -zcat archive/@value{GDB-RTEMSPATCH} | 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 - -@section Using the bit_gdb script - -The simplest way to build gdb for RTEMS is to use the @code{bit_gdb} script. -This script interprets the settings in the @code{user.cfg} file to -produce the gdb configuration most appropriate for the target CPU. - -This script is invoked as follows: - -@example -./bit_gdb CPU -@end example - -Where CPU is one of the RTEMS supported CPU families from the following -list: - -@itemize @bullet -@item hppa1.1 -@item i386 -@item i386-elf -@item i386-go32 -@item i960 -@item m68k -@item mips64orion -@item powerpc -@item sh -@item sparc -@end itemize - -If gdb supports a CPU instruction simulator for this configuration, then -it is included in the build. - -@section Using the gdb configure Script Directly - -@subsection GDB with Sparc Instruction Simulation (SIS) - -@subheading Make the Build Directory - -Create a build directory for the SIS Debugger - -@example -cd tools -mkdir build-sis -@end example - -@subheading Configure for the Build - -Configure the GNU Debugger for the -Sparc Instruction Simulator (SIS): - -@example -cd tools/build-sis -../@value{GDB-UNTAR}/configure --target-sparc-erc32-aout \ - --program-prefix=sparc-rtems- \ - --disable-gdbtk \ - --enable-targets=all \ - --prefix=<INSTALL_POINT_FOR_SIS> -@end example - -Where <INSTALL_POINT_FOR_SIS> is a unique location where the gdb -with SIS will be created. - -@subheading Make the Debugger - -From tools/build-sis execute the following command sequence: - -@example -gmake all install -@end example - - -@subsection GDB with PowerPC Instruction Simulator - -@subheading Make the Build Directory - -Create a build directory for the SIS Debugger - -@example -cd tools -mkdir build-ppc -@end example - -@subheading Configure for the Build - -Configure the GNU Debugger for the PowerPC -Instruction Simulator (PSIM): - -@example -cd tools/build-ppc -../@value{GDB-UNTAR}/configure \ - --target=powerpc-unknown-eabi \ - --program-prefix=powerpc-rtems- \ - --enable-sim-powerpc \ - --enable-sim-timebase \ - --enable-sim-inline \ - --enable-sim-hardware \ - --enable-targets=all \ - --prefix=<INSTALL_POINT_FOR_PPC> -@end example - -Where <INSTALL_POINT_FOR_PPC> is a unique location where the gdb -with PSIM will be created. - - -@subheading Make the Debugger - -From tools/build-ppc execute the following command sequence: - -@example -gmake all install -@end example - - -@subsection GDB for DINK32 - -@subheading Make the Build Directory - -Create a build directory for the DINK32 Debugger - -@example -cd tools -mkdir build-dink32 -@end example - -@subheading Configure for the Build - -Configure the GNU Debugger to communicate with -the DINK32 ROM monitor: - -@example -cd tools/build-dink32 -../@value{GDB-UNTAR}/configure --target-powerpc-elf \ - --program-prefix=powerpc-rtems- \ - --enable-targets=all \ - --prefix=<INSTALL_POINT_FOR_DINK32> -@end example - -Where <INSTALL_POINT_FOR_DINK32> is a unique location where the -gdb Dink32 will be created. - -@subheading Make the Debugger - -From tools/build-dink32 execute the following command sequence: - -@example -gmake all install -@end example - |