source: rtems/doc/started/gdb.t @ bdec2709

4.104.114.84.95
Last change on this file since bdec2709 was bdec2709, checked in by Joel Sherrill <joel.sherrill@…>, on 04/10/98 at 16:03:26

In texinfo nicely with all version dependent information
now in variables and some updates already in place.

  • Property mode set to 100644
File size: 3.9 KB
Line 
1@c
2@c  COPYRIGHT (c) 1988-1998.
3@c  On-Line Applications Research Corporation (OAR).
4@c  All rights reserved.
5@c
6@c  $Id$
7@c
8
9@chapter Building the GNU Debugger
10
11GDB is not currently RTEMS aware. The following configurations have been
12successfully used with RTEMS applications:
13
14@itemize bullet
15@item Sparc Instruction Simulator (SIS)
16@item PowerPC Instruction Simulator (PSIM)
17@item DINK32
18@end itemize
19
20Other configurations of gdb have successfully been used by RTEMS users
21but are not documented here.
22
23@section Unarchive the gdb distribution
24
25Use the following commands to unarchive the gdb distribution:
26
27@example
28cd tools
29tar xzf ../arc/@value{GDB-TAR}
30@end example
31
32@c
33@c  GDB Patch
34@c
35
36@section Apply RTEMS Patch to GDB
37
38@ifclear GDB-RTEMSPATCH
39No RTEMS specific patches are required for @value{GDB-VERSION} to
40support @value{RTEMS-VERSION}.
41@end ifclear
42
43@ifset GDB-RTEMSPATCH
44
45Apply the patch using the following command sequence:
46
47@example
48cd tools/@value{GDB-UNTAR}
49zcat arc/@value{GDB-RTEMSPATCH} | patch -p1
50@end example
51
52Check to see if any of these patches have been rejected using the following
53sequence:
54
55@example
56cd tools/@value{GDB-UNTAR}
57find . -name "*.rej" -print
58@end example
59
60If any files are found with the .rej extension, a patch has been rejected.
61This should not happen with a good patch file.
62
63To see the files that have been modified use the sequence:
64
65@example
66cd tools/@value{GDB-UNTAR}
67find . -name "*.orig" -print
68@end example
69
70The files that are found, have been modified by the patch file.
71
72@end ifset
73
74
75@section GDB with Sparc Instruction Simulation (SIS)
76
77The directory @value{GDB-UNTAR} is created under the tools directory.
78
79@subheading Make the build directory
80
81Create a build directory for the SIS Debugger
82
83@example
84cd tools
85mkdir build-sis
86@end example
87
88@subheading Configure for the build
89
90Configure the GNU Debugger for the
91Sparc Instruction Simulator (SIS):
92
93@example
94cd tools/build-sis
95../@value{GDB-UNTAR}/configure --target-sparc-erc32-aout \
96    --program-prefix=sparc-rtems- \
97    --disable-gdbtk \
98    --enable-targets=all \
99    --prefix=<INSTALL_POINT_FOR_SIS>
100@end example
101
102Where <INSTALL_POINT_FOR_SIS> is a unique location where the gdb
103with SIS will be created.
104
105@subheading Make the debugger
106
107From tools/build-sis execute the following command sequence:
108
109@example
110gmake all install
111@end example
112
113
114@section GDB with PowerPC Instruction Simulator
115
116@subheading Make the build directory
117
118Create a build directory for the SIS Debugger
119
120@example
121cd tools
122mkdir build-ppc
123@end example
124
125@subheading Configure for the build
126
127Configure the GNU Debugger for the PowerPC
128Instruction Simulator (PSIM):
129
130@example
131cd tools/build-ppc
132../@value{GDB-UNTAR}/configure \
133      --target=powerpc-unknown-eabi \
134      --program-prefix=powerpc-rtems- \
135      --enable-sim-powerpc \
136      --enable-sim-timebase \
137      --enable-sim-inline \
138      --enable-sim-hardware \
139      --enable-targets=all \
140      --prefix=<INSTALL_POINT_FOR_PPC>
141@end example
142
143Where <INSTALL_POINT_FOR_PPC> is a unique location where the gdb
144with PSIM will be created.
145
146
147@subheading Make the debugger
148
149From tools/build-ppc execute the following command sequence:
150
151@example
152gmake all install
153@end example
154
155
156@section GDB with Dink32
157
158@subheading Unarchive the gdb distribution
159
160Use the following commands to unarchive the gdb distribution:
161
162@subheading Make the build directory
163
164Create a build directory for the DINK32 Debugger
165
166@example
167cd tools
168mkdir build-dink32
169@end example
170
171@subheading Configure for the build
172
173Configure the GNU Debugger to communicate with
174the DINK32 ROM monitor:
175
176@example
177cd tools/build-dink32
178../@value{GDB-UNTAR}/configure --target-powerpc-elf \
179    --program-prefix=powerpc-rtems- \
180    --enable-targets=all \
181    --prefix=<INSTALL_POINT_FOR_DINK32>
182@end example
183
184Where <INSTALL_POINT_FOR_DINK32> is a unique location where the
185gdb Dink32 will be created.
186
187@subheading Make the debugger
188
189From tools/build-dink32 execute the following command sequence:
190
191@example
192gmake all install
193@end example
194
Note: See TracBrowser for help on using the repository browser.