mingw/info/gdb/KOD.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="KOD">KOD</a>,
  13 Previous:<a rel="previous" accesskey="p" href="Remote.html#Remote">Remote</a>,
  14 Up:<a rel="up" accesskey="u" href="Targets.html#Targets">Targets</a>
  15 <hr><br>
  16 </div>
  17
  18 <h3 class="section">Kernel Object Display</h3>
  19
  20    <p>Some targets support kernel object display.  Using this facility,
  21 GDB communicates specially with the underlying operating system
  22 and can display information about operating system-level objects such as
  23 mutexes and other synchronization objects.  Exactly which objects can be
  24 displayed is determined on a per-OS basis.
  25
  26    <p>Use the <code>set os</code> command to set the operating system.  This tells
  27 GDB which kernel object display module to initialize:
  28
  29 <pre class="example">     (gdb) set os cisco
  30      </pre>
  31
  32    <p>If <code>set os</code> succeeds, GDB will display some information
  33 about the operating system, and will create a new <code>info</code> command
  34 which can be used to query the target.  The <code>info</code> command is named
  35 after the operating system:
  36
  37 <pre class="example">     (gdb) info cisco
  38      List of Cisco Kernel Objects
  39      Object     Description
  40      any        Any and all objects
  41      </pre>
  42
  43    <p>Further subcommands can be used to query about particular objects known
  44 by the kernel.
  45
  46    <p>There is currently no way to determine whether a given operating system
  47 is supported other than to try it.
  48
  49    </body></html>
  50