mingw/info/gdb/GDB-Bugs.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="GDB%20Bugs">GDB Bugs</a>,
  13 Next:<a rel="next" accesskey="n" href="Formatting-Documentation.html#Formatting%20Documentation">Formatting Documentation</a>,
  14 Previous:<a rel="previous" accesskey="p" href="GDB-MI.html#GDB%2fMI">GDB/MI</a>,
  15 Up:<a rel="up" accesskey="u" href="index.html#Top">Top</a>
  16 <hr><br>
  17 </div>
  18
  19 <h2 class="chapter">Reporting Bugs in GDB</h2>
  20
  21    <p>Your bug reports play an essential role in making GDB reliable.
  22
  23    <p>Reporting a bug may help you by bringing a solution to your problem, or it
  24 may not.  But in any case the principal function of a bug report is to help
  25 the entire community by making the next version of GDB work better.  Bug
  26 reports are your contribution to the maintenance of GDB.
  27
  28    <p>In order for a bug report to serve its purpose, you must include the
  29 information that enables us to fix the bug.
  30
  31 <ul class="menu">
  32 <li><a accesskey="1" href="Bug-Criteria.html#Bug%20Criteria">Bug Criteria</a>:                 Have you found a bug?
  33 <li><a accesskey="2" href="Bug-Reporting.html#Bug%20Reporting">Bug Reporting</a>:                How to report bugs
  34 </ul>
  35
  36    </body></html>
  37