mingw/info/gdbint/Support-Libraries.html

   1 <html lang="en">
   2 <head>
   3 <title>GDB Internals</title>
   4 <meta http-equiv="Content-Type" content="text/html">
   5 <meta name="description" content="GDB Internals">
   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="Support%20Libraries">Support Libraries</a>,
  13 Next:<a rel="next" accesskey="n" href="Coding.html#Coding">Coding</a>,
  14 Previous:<a rel="previous" accesskey="p" href="Native-Debugging.html#Native%20Debugging">Native Debugging</a>,
  15 Up:<a rel="up" accesskey="u" href="index.html#Top">Top</a>
  16 <hr><br>
  17 </div>
  18
  19 <h2 class="chapter">Support Libraries</h2>
  20
  21 <h3 class="section">BFD</h3>
  22
  23    <p>BFD provides support for GDB in several ways:
  24
  25      <dl>
  26 <dt><em>identifying executable and core files</em>
  27      <dd>BFD will identify a variety of file types, including a.out, coff, and
  28 several variants thereof, as well as several kinds of core files.
  29
  30      <br><dt><em>access to sections of files</em>
  31      <dd>BFD parses the file headers to determine the names, virtual addresses,
  32 sizes, and file locations of all the various named sections in files
  33 (such as the text section or the data section).  GDB simply
  34 calls BFD to read or write section <var>x</var> at byte offset <var>y</var> for
  35 length <var>z</var>.
  36
  37      <br><dt><em>specialized core file support</em>
  38      <dd>BFD provides routines to determine the failing command name stored in a
  39 core file, the signal with which the program failed, and whether a core
  40 file matches (i.e. could be a core dump of) a particular executable
  41 file.
  42
  43      <br><dt><em>locating the symbol information</em>
  44      <dd>GDB uses an internal interface of BFD to determine where to find the
  45 symbol information in an executable file or symbol-file.  GDB itself
  46 handles the reading of symbols, since BFD does not "understand" debug
  47 symbols, but GDB uses BFD's cached information to find the symbols,
  48 string table, etc.
  49 </dl>
  50
  51 <h3 class="section">opcodes</h3>
  52
  53    <p>The opcodes library provides GDB's disassembler.  (It's a separate
  54 library because it's also used in binutils, for <code>objdump</code>).
  55
  56 <h3 class="section">readline</h3>
  57
  58 <h3 class="section">mmalloc</h3>
  59
  60 <h3 class="section">libiberty</h3>
  61
  62 <h3 class="section">gnu-regex</h3>
  63
  64    <p>Regex conditionals.
  65
  66      <dl>
  67 <dt><code>C_ALLOCA</code>
  68      <dd>
  69 <br><dt><code>NFAILURES</code>
  70      <dd>
  71 <br><dt><code>RE_NREGS</code>
  72      <dd>
  73 <br><dt><code>SIGN_EXTEND_CHAR</code>
  74      <dd>
  75 <br><dt><code>SWITCH_ENUM_BUG</code>
  76      <dd>
  77 <br><dt><code>SYNTAX_TABLE</code>
  78      <dd>
  79 <br><dt><code>Sword</code>
  80      <dd>
  81 <br><dt><code>sparc</code>
  82      <dd></dl>
  83
  84 <h3 class="section">include</h3>
  85
  86    </body></html>
  87