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=
"Bug%20Criteria">Bug Criteria
</a>,
13 Next:
<a rel=
"next" accesskey=
"n" href=
"Bug-Reporting.html#Bug%20Reporting">Bug Reporting
</a>,
14 Up:
<a rel=
"up" accesskey=
"u" href=
"GDB-Bugs.html#GDB%20Bugs">GDB Bugs
</a>
18 <h3 class=
"section">Have you found a bug?
</h3>
20 <p>If you are not sure whether you have found a bug, here are some guidelines:
23 <li>If the debugger gets a fatal signal, for any input whatever, that is a
24 GDB bug. Reliable debuggers never crash.
26 <li>If GDB produces an error message for valid input, that is a
27 bug. (Note that if you're cross debugging, the problem may also be
28 somewhere in the connection to the target.)
30 <li>If GDB does not produce an error message for invalid input,
31 that is a bug. However, you should note that your idea of
32 "invalid input" might be our idea of
"an extension" or
"support
33 for traditional practice".
35 <li>If you are an experienced user of debugging tools, your suggestions
36 for improvement of GDB are welcome in any case.