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=
"VxWorks%20Connection">VxWorks Connection
</a>,
13 Next:
<a rel=
"next" accesskey=
"n" href=
"VxWorks-Download.html#VxWorks%20Download">VxWorks Download
</a>,
14 Up:
<a rel=
"up" accesskey=
"u" href=
"VxWorks.html#VxWorks">VxWorks
</a>
18 <h5 class=
"subsubsection">Connecting to VxWorks
</h5>
20 <p>The GDB command
<code>target
</code> lets you connect to a VxWorks target on the
21 network. To connect to a target whose host name is
"<code>tt</code>", type:
23 <pre class=
"example"> (vxgdb) target vxworks tt
26 GDB displays messages like these:
28 <pre class=
"smallexample"> Attaching remote machine across net...
32 GDB then attempts to read the symbol tables of any object modules
33 loaded into the VxWorks target since it was last booted. GDB locates
34 these files by searching the directories listed in the command search
35 path (see
<a href=
"Environment.html#Environment">Your program's environment
</a>); if it fails
36 to find an object file, it displays a message such as:
38 <pre class=
"example"> prog.o: No such file or directory.
41 <p>When this happens, add the appropriate directory to the search path with
42 the GDB command
<code>path
</code>, and execute the
<code>target
</code>