blob: 64225fb4f5c976fb64d7d1c604dfe8683a56ef02 (
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
77
78
79
80
81
|
<!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 - Program Settings</title>
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><a href="index.html">Contents</a></p>
<h1>
The Program Settings Dialog</h1>
<p>In this dialog, program specific settings can be selected. It is invoked
by <i>Settings|This Program</i>. The settings apply only to the currently loaded
executable and will be saved across sessions.</p>
<blockquote><b><i>Important note:</i></b> The chosen settings will only
apply the next time the executable is loaded into KDbg. This means that
after pressing
<i>OK</i> in this dialog, you must reload the executable
using <i>File|Recent Executables</i>!!</blockquote>
<ul>
<li>
<a href="#driver">Debugger</a></li>
<li>
<a href="#output">Output</a></li>
</ul>
<h2>
<a name="driver"></a>Debugger</h2>
<p>In this section, the debugger to be used for the program can be chosen.</p>
<h4>
How to invoke GDB</h4>
<blockquote>Enter the command to invoke gdb. Leave this field empty to
use the default gdb command as specified in the <a href="globaloptions.html">global
options</a>. When you are cross-compiling and remote-debugging, you will
probably want to use a different gdb suitable for the target platform.
The default command is <tt>gdb --fullname --nx</tt>. Be sure to specify
at least <tt>--fullname</tt> if you change the gdb command.
If you remove this command switch, KDbg will not work.
</blockquote>
<h2>
<a name="output"></a>Output</h2>
<p>In this section, the terminal emulation under which the program will run
can be selected.</p>
<h4>
No input and output</h4>
<blockquote>Check this option if your program does not receive input from
the terminal and you do not want to see the output that the program writes
to <tt>stdout</tt> and <tt>stderr</tt> (if any). All three standard channels
(<tt>stdin</tt>, <tt>stdout</tt>, and <tt>stderr</tt>) are effectively
redirected to <tt>/dev/null</tt>.</blockquote>
<h4>
Only output, simple terminal emulation</h4>
<blockquote>Check this option if your program does not receive input from
the terminal (<tt>stdin</tt> will be redirected to <tt>/dev/null</tt>),
and the output that it writes to <tt>stdout</tt> and <tt>stderr</tt> does
not require sophisticated terminal emulation. The output will be shown
in the <a href="pgmoutput.html">Output window</a>.
<br><i>Important:</i> The integrated terminal emulator will only interpret
the line-feed character <tt>\n</tt> (ASCII 10) to break lines. It will
<em>not</em>
handle the carriage-return character <tt>\r</tt> (ASCII 13). This is sufficient
for displaying plain debugging output that is often used by developers
of GUI programs.</blockquote>
<h4>
Full terminal emulation</h4>
<blockquote>Check this option if your program reads input from <tt>stdin</tt>
or if the output to <tt>stdout</tt> or <tt>stderr</tt> requires terminal
emulation. A terminal emulator will be invoked as specified in the <a href="globaloptions.html">global
options</a>.</blockquote>
</body>
</html>
|
