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=
"Altering">Altering
</a>,
13 Next:
<a rel=
"next" accesskey=
"n" href=
"GDB-Files.html#GDB%20Files">GDB Files
</a>,
14 Previous:
<a rel=
"previous" accesskey=
"p" href=
"Symbols.html#Symbols">Symbols
</a>,
15 Up:
<a rel=
"up" accesskey=
"u" href=
"index.html#Top">Top
</a>
19 <h2 class=
"chapter">Altering Execution
</h2>
21 <p>Once you think you have found an error in your program, you might want to
22 find out for certain whether correcting the apparent error would lead to
23 correct results in the rest of the run. You can find the answer by
24 experiment, using the GDB features for altering execution of the
27 <p>For example, you can store new values into variables or memory
28 locations, give your program a signal, restart it at a different
29 address, or even return prematurely from a function.
32 <li><a accesskey=
"1" href=
"Assignment.html#Assignment">Assignment
</a>: Assignment to variables
33 <li><a accesskey=
"2" href=
"Jumping.html#Jumping">Jumping
</a>: Continuing at a different address
34 <li><a accesskey=
"3" href=
"Signaling.html#Signaling">Signaling
</a>: Giving your program a signal
35 <li><a accesskey=
"4" href=
"Returning.html#Returning">Returning
</a>: Returning from a function
36 <li><a accesskey=
"5" href=
"Calling.html#Calling">Calling
</a>: Calling your program's functions
37 <li><a accesskey=
"6" href=
"Patching.html#Patching">Patching
</a>: Patching your program