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=
"C%20Checks">C Checks
</a>,
13 Next:
<a rel=
"next" accesskey=
"n" href=
"Debugging-C.html#Debugging%20C">Debugging C
</a>,
14 Previous:
<a rel=
"previous" accesskey=
"p" href=
"C-Defaults.html#C%20Defaults">C Defaults
</a>,
15 Up:
<a rel=
"up" accesskey=
"u" href=
"C.html#C">C
</a>
19 <h5 class=
"subsubsection">C and C
<tt>++
</tt> type and range checks
</h5>
21 <p>By default, when GDB parses C or C
<tt>++
</tt> expressions, type checking
22 is not used. However, if you turn type checking on, GDB
23 considers two variables type equivalent if:
26 <li>The two variables are structured and have the same structure, union, or
29 <li>The two variables have the same type name, or types that have been
30 declared equivalent through
<code>typedef
</code>.
34 <p>Range checking, if turned on, is done on mathematical operations. Array
35 indices are not checked, since they are often used to index a pointer
36 that is not itself an array.