3 <title>Debugging with GDB
</title>
4 <meta http-equiv=
"Content-Type" content=
"text/html">
5 <meta name=
"description" content=
"Debugging with GDB">
6 <meta name=
"generator" content=
"makeinfo 4.3">
7 <link href=
"http://www.gnu.org/software/texinfo/" rel=
"generator-home">
12 Node:
<a name=
"Targets">Targets
</a>,
13 Next:
<a rel=
"next" accesskey=
"n" href=
"Remote-Debugging.html#Remote%20Debugging">Remote Debugging
</a>,
14 Previous:
<a rel=
"previous" accesskey=
"p" href=
"GDB-Files.html#GDB%20Files">GDB Files
</a>,
15 Up:
<a rel=
"up" accesskey=
"u" href=
"index.html#Top">Top
</a>
19 <h2 class=
"chapter">Specifying a Debugging Target
</h2>
21 <p>A
<dfn>target
</dfn> is the execution environment occupied by your program.
23 <p>Often, GDB runs in the same host environment as your program;
24 in that case, the debugging target is specified as a side effect when
25 you use the
<code>file
</code> or
<code>core
</code> commands. When you need more
26 flexibility--for example, running GDB on a physically separate
27 host, or controlling a standalone system over a serial port or a
28 realtime system over a TCP/IP connection--you can use the
<code>target
</code>
29 command to specify one of the target types configured for GDB
30 (see
<a href=
"Target-Commands.html#Target%20Commands">Commands for managing targets
</a>).
33 <li><a accesskey=
"1" href=
"Active-Targets.html#Active%20Targets">Active Targets
</a>: Active targets
34 <li><a accesskey=
"2" href=
"Target-Commands.html#Target%20Commands">Target Commands
</a>: Commands for managing targets
35 <li><a accesskey=
"3" href=
"Byte-Order.html#Byte%20Order">Byte Order
</a>: Choosing target byte order
36 <li><a accesskey=
"4" href=
"Remote.html#Remote">Remote
</a>: Remote debugging
37 <li><a accesskey=
"5" href=
"KOD.html#KOD">KOD
</a>: Kernel Object Display