kdbg/doc/en/howdoi.html

   1 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
   2 <html>
   3 <head>
   4    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
   5    <meta name="GENERATOR" content="Mozilla/4.74 [en] (X11; U; Linux 2.2.16-SMP i686) [Netscape]">
   6    <meta name="Author" content="Johannes Sixt">
   7    <title>KDbg - User's Manual - How Do I...?</title>
   8 </head>
   9 <body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E" alink="#FF0000">
  10 <a href="index.html">Contents</a>
  11 <h1>
  12 How Do I...?</h1>
  13
  14 <h4>
  15 ... set breakpoints?</h4>
  16 There's more than one way to set a breakpoint:
  17 <ul>
  18 <li>
  19 You can set it in the source window by clicking on the "active area" at
  20 the far left of the line.</li>
  21
  22 <li>
  23 You can set it by selecting the line in the source window and choosing
  24 an option from the <i>Breakpoint</i> menu.</li>
  25
  26 <li>
  27 You can set it in the <a href="breakptlist.html">breakpoint list</a>.</li>
  28 </ul>
  29 If you can't set breakpoints, maybe the program is currently running. You
  30 can't set breakpoints while the program is running. Stop it first using
  31 <i>Execution|Break</i>.
  32 If you still can't set breakpoints, make sure that you have compiled <i>and
  33 linked</i> your program with debugging information enabled.
  34 <h4>
  35 ... display the value of a global variable or an arbitrary expression?</h4>
  36 Use the Watch window.
  37 <h4>
  38 ... set watchpoints?</h4>
  39 Watchpoints are manipulated in the <a href="breakptlist.html">breakpoint
  40 list</a>.
  41 <h4>
  42 ... use a core dump?</h4>
  43 First load the executable using <i>File|Executable</i>, then specify the
  44 core dump using <i>File|Core dump</i>.
  45 <h4>
  46 ... debug a program that's caught in an endless loop?</h4>
  47 Start the program and let it run until it is in the endless loop. Then
  48 switch to KDbg and choose <i>Execution|Break</i>. You've just caught the
  49 nasty program <i>in flagranti</i>!
  50 <h4>
  51 ... achieve that the program passes over a breakpoint a number of times
  52 before it stops?</h4>
  53 In the <a href="breakptlist.html">breakpoint list</a> select the breakpoint;
  54 then click <i>Conditional</i> and specify the number of times to skip the
  55 breakpoint in the <i>Ignore count</i> field.
  56 <h4>
  57 ... set environment variables for the executable?</h4>
  58 Select <i>Execution|Arguments</i> and specify the environment variables
  59 in the <a href="argspwdenv.html#Environment">program arguments dialog</a>.
  60 <h4>
  61 ... set a working directory for the executable?</h4>
  62 Select <i>Execution|Arguments</i> and specify the working directory in
  63 the <a href="argspwdenv.html#WorkingDir">program arguments dialog</a>.
  64 <h4>
  65 ... get rid of this terminal window?</h4>
  66 Select <i>File|Settings</i> and switch to the <a href="pgmsettings.html#output">Output
  67 </a>tab.
  68 Select <i>Only output, simple terminal emulation</i> and click
  69 <i>OK</i>.
  70 Now restart the program (choose it from the list under <i>File|Recent Executables</i>).
  71 The program output goes now to the built-in <a href="pgmoutput.html">output
  72 window</a> and stdin is redirected to <tt>/dev/null</tt>.
  73 <p>You must do this for every new program that you debug.
  74 <p><b><i>Important:</i></b> You should not do this if your program expects
  75 input from the terminal (usually stdin) or if its output requires nifty
  76 terminal emulation (more than carriage-return and line-feed). The built-in
  77 output window does not support input and terminal emulation.
  78 </body>
  79 </html>