mingw/info/gdb/VxWorks.html

   1 <html lang="en">
   2 <head>
   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">
   8 </head>
   9 <body>
  10 <div class="node">
  11 <p>
  12 Node:<a name="VxWorks">VxWorks</a>,
  13 Up:<a rel="up" accesskey="u" href="Embedded-OS.html#Embedded%20OS">Embedded OS</a>
  14 <hr><br>
  15 </div>
  16
  17 <h4 class="subsection">Using GDB with VxWorks</h4>
  18
  19      <dl>
  20
  21      <br><dt><code>target vxworks </code><var>machinename</var><code></code>
  22      <dd>A VxWorks system, attached via TCP/IP.  The argument <var>machinename</var>
  23 is the target system's machine name or IP address.
  24
  25    </dl>
  26
  27    <p>On VxWorks, <code>load</code> links <var>filename</var> dynamically on the
  28 current target system as well as adding its symbols in GDB.
  29
  30    GDB enables developers to spawn and debug tasks running on networked
  31 VxWorks targets from a Unix host.  Already-running tasks spawned from
  32 the VxWorks shell can also be debugged.  GDB uses code that runs on
  33 both the Unix host and on the VxWorks target.  The program
  34 <code>gdb</code> is installed and executed on the Unix host.  (It may be
  35 installed with the name <code>vxgdb</code>, to distinguish it from a
  36 GDB for debugging programs on the host itself.)
  37
  38      <dl>
  39 <dt><code>VxWorks-timeout </code><var>args</var><code></code>
  40      <dd>All VxWorks-based targets now support the option <code>vxworks-timeout</code>.
  41 This option is set by the user, and  <var>args</var> represents the number of
  42 seconds GDB waits for responses to rpc's.  You might use this if
  43 your VxWorks target is a slow software simulator or is on the far side
  44 of a thin network line.
  45 </dl>
  46
  47    <p>The following information on connecting to VxWorks was current when
  48 this manual was produced; newer releases of VxWorks may use revised
  49 procedures.
  50
  51    <p>To use GDB with VxWorks, you must rebuild your VxWorks kernel
  52 to include the remote debugging interface routines in the VxWorks
  53 library <code>rdb.a</code>.  To do this, define <code>INCLUDE_RDB</code> in the
  54 VxWorks configuration file <code>configAll.h</code> and rebuild your VxWorks
  55 kernel.  The resulting kernel contains <code>rdb.a</code>, and spawns the
  56 source debugging task <code>tRdbTask</code> when VxWorks is booted.  For more
  57 information on configuring and remaking VxWorks, see the manufacturer's
  58 manual.
  59
  60    <p>Once you have included <code>rdb.a</code> in your VxWorks system image and set
  61 your Unix execution search path to find GDB, you are ready to
  62 run GDB.  From your Unix host, run <code>gdb</code> (or
  63 <code>vxgdb</code>, depending on your installation).
  64
  65    GDB comes up showing the prompt:
  66
  67 <pre class="example">     (vxgdb)
  68      </pre>
  69
  70 <ul class="menu">
  71 <li><a accesskey="1" href="VxWorks-Connection.html#VxWorks%20Connection">VxWorks Connection</a>:           Connecting to VxWorks
  72 <li><a accesskey="2" href="VxWorks-Download.html#VxWorks%20Download">VxWorks Download</a>:             VxWorks download
  73 <li><a accesskey="3" href="VxWorks-Attach.html#VxWorks%20Attach">VxWorks Attach</a>:               Running tasks
  74 </ul>
  75
  76    </body></html>
  77