mingw/info/gdb/Kill-Process.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="Kill%20Process">Kill Process</a>,
  13 Next:<a rel="next" accesskey="n" href="Threads.html#Threads">Threads</a>,
  14 Previous:<a rel="previous" accesskey="p" href="Attach.html#Attach">Attach</a>,
  15 Up:<a rel="up" accesskey="u" href="Running.html#Running">Running</a>
  16 <hr><br>
  17 </div>
  18
  19 <h3 class="section">Killing the child process</h3>
  20
  21      <dl>
  22 <dt><code>kill</code>
  23      <dd>Kill the child process in which your program is running under GDB.
  24 </dl>
  25
  26    <p>This command is useful if you wish to debug a core dump instead of a
  27 running process.  GDB ignores any core dump file while your program
  28 is running.
  29
  30    <p>On some operating systems, a program cannot be executed outside GDB
  31 while you have breakpoints set on it inside GDB.  You can use the
  32 <code>kill</code> command in this situation to permit running your program
  33 outside the debugger.
  34
  35    <p>The <code>kill</code> command is also useful if you wish to recompile and
  36 relink your program, since on many systems it is impossible to modify an
  37 executable file while it is running in a process.  In this case, when you
  38 next type <code>run</code>, GDB notices that the file has changed, and
  39 reads the symbol table again (while trying to preserve your current
  40 breakpoint settings).
  41
  42    </body></html>
  43