summaryrefslogtreecommitdiffstats
path: root/doc/en/howdoi.html
blob: 6191144e1af2cfb2fe663324ffa77849ecf35255 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
   <meta name="Author" content="Johannes Sixt">
   <title>KDbg - User's Manual - How Do I...?</title>
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><a href="index.html">Contents</a></p>
<h1>
How Do I...?</h1>

<h4>
... set breakpoints?</h4>
<p>There's more than one way to set a breakpoint:</p>
<ul>
<li>
You can set it in the source window by clicking on the "active area" at
the far left of the line.</li>

<li>
You can set it by selecting the line in the source window and choosing
an option from the <i>Breakpoint</i> menu.</li>

<li>
You can set it in the <a href="breakptlist.html">breakpoint list</a>.</li>
</ul>
<p>If you can't set breakpoints, maybe the program is currently running. You
can't set breakpoints while the program is running. Stop it first using
<i>Execution|Break</i>.
If you still can't set breakpoints, make sure that you have compiled <em>and
linked</em> your program with debugging information enabled.</p>
<h4>
... display the value of a global variable or an arbitrary expression?</h4>
<p>Use the <A href="watches.html">Watch window</A>.</p>
<h4>
... set watchpoints?</h4>
<p>Watchpoints are manipulated in the <a href="breakptlist.html">breakpoint
list</a>.</p>
<h4>
... use a core dump?</h4>
<p>First load the executable using <i>File|Executable</i>, then specify the
core dump using <i>File|Core dump</i>.</p>
<h4>
... debug a program that's caught in an endless loop?</h4>
<p>Start the program and let it run until it is in the endless loop. Then
switch to KDbg and choose <i>Execution|Break</i>. You've just caught the
nasty program <em>in flagranti</em>!</p>
<h4>
... achieve that the program passes over a breakpoint a number of times
before it stops?</h4>
<p>In the <a href="breakptlist.html">breakpoint list</a> select the breakpoint;
then click <i>Conditional</i> and specify the number of times to skip the
breakpoint in the <i>Ignore count</i> field.</p>
<h4>
... set environment variables for the executable?</h4>
<p>Select <i>Execution|Arguments</i> and specify the environment variables
in the <a href="argspwdenv.html#Environment">program arguments dialog</a>.</p>
<h4>
... set a working directory for the executable?</h4>
<p>Select <i>Execution|Arguments</i> and specify the working directory in
the <a href="argspwdenv.html#WorkingDir">program arguments dialog</a>.</p>
<h4>
... get rid of this terminal window?</h4>
<p>Select <i>Settings|This Program</i> and switch to the <a href="pgmsettings.html#output">Output</a> tab.
Select <i>Only output, simple terminal emulation</i> and click <i>OK</i>.
Now restart the program (choose it from the list under <i>File|Recent Executables</i>).
The program output goes now to the built-in <a href="pgmoutput.html">output
window</a> and stdin is redirected to <tt>/dev/null</tt>.</p>
<p>You must do this for every new program that you debug.</p>
<p><b><i>Important:</i></b> You should not do this if your program expects
input from the terminal (usually stdin) or if its output requires nifty
terminal emulation (more than carriage-return and line-feed). The built-in
output window does not support input and terminal emulation.</p>
</body>
</html>