1 |
578 |
markom |
<HTML>
|
2 |
|
|
<HEAD>
|
3 |
|
|
<TITLE>Console Window Help</TITLE>
|
4 |
|
|
</HEAD>
|
5 |
|
|
<BODY>
|
6 |
|
|
<CENTER><H2>The Console Window</H2></CENTER>
|
7 |
|
|
|
8 |
|
|
<P>The Console Window provides the traditional command-line interface to GDB.
|
9 |
|
|
It is very similar to the command-line you get when GDB is run with "-nw".</P>
|
10 |
|
|
|
11 |
|
|
<UL>
|
12 |
|
|
<LI><A HREF="#display">Console Display</A></LI>
|
13 |
|
|
<LI><A HREF="#editing">Editing Commands</A></LI>
|
14 |
|
|
<LI><A HREF="#history">History Commands</A></LI>
|
15 |
|
|
<LI><A HREF="#display_hlp">Getting Help</A></LI>
|
16 |
|
|
</UL>
|
17 |
|
|
|
18 |
|
|
<H4><A NAME="display">Console Display</A></H4>
|
19 |
|
|
The Console Display is simply a scrolled window in which the debugger prompt
|
20 |
|
|
appears. By default, the prompt is set to "(gdb) ", but it may be changed via a
|
21 |
|
|
command line option.
|
22 |
|
|
|
23 |
|
|
<P>To execute commands in the console window, simply enter
|
24 |
|
|
the command in the display. If the debugger is busy, the message "Error: The
|
25 |
|
|
debugger is busy." appears informing the user that the command was not accepted.</P>
|
26 |
|
|
|
27 |
|
|
<P>Whenever a command is executed, the debugger's windows will update to display
|
28 |
|
|
any new state information. Any output from the command is also echoed to the Console
|
29 |
|
|
Window for ease of use. If an error occurs, an error message is printed to the Console
|
30 |
|
|
Window. All error messages appear in the Console Window using a red typeface.
|
31 |
|
|
</P>
|
32 |
|
|
|
33 |
|
|
<BR>
|
34 |
|
|
|
35 |
|
|
<H4><A NAME="editing">Editing Commands</A></H4>
|
36 |
|
|
<P>The Console Window shell has many powerful features to help edit commands.</P>
|
37 |
|
|
<UL>
|
38 |
|
|
<LI> Return or Enter causes the command to be executed.
|
39 |
|
|
|
40 |
|
|
<LI> Control-A moves the cursor to the beginning of the line.</LI>
|
41 |
|
|
<LI> Control-E moves the cursor to the end of the line.</LI>
|
42 |
|
|
<LI> Control-D or DELETE delete the character to the right of the cursor.</LI>
|
43 |
|
|
<LI> BACKSPACE deletes the character to the left of the cursor.</LI>
|
44 |
|
|
<LI> Control-B or LeftArrow moves the cursor to the left.</LI>
|
45 |
|
|
<LI> Control-F or RightArrow moves the cursor to the right.</LI>
|
46 |
|
|
<LI> Control-K deletes everything to the right of the cursor.</LI>
|
47 |
|
|
<LI> Control-U deletes the text between the cursor and the start of the line.</LI>
|
48 |
|
|
<LI> Control-W deletes the previous word</LI>
|
49 |
|
|
<LI> END deletes the whole line.</LI>
|
50 |
|
|
<LI> The mouse may also be used to position the cursor and cut and paste.</LI>
|
51 |
|
|
</UL>
|
52 |
|
|
|
53 |
|
|
<H4><A NAME="history">History Commands</A></H4>
|
54 |
|
|
<UL>
|
55 |
|
|
<LI> Conrol-P or UpArrow recalls the previous command.</LI>
|
56 |
|
|
<LI> Conrol-N or DownArrow recalls the next command.</LI>
|
57 |
|
|
<LI> Shift-UpArrow or Control-UpArrow will search through previous commands
|
58 |
|
|
for commands that start with the same characters as the current line. For
|
59 |
|
|
example, if you type "pr" and hit Shift-UpArrow, it may find commands in the
|
60 |
|
|
history such as "print foo" or "print sol[x]". Each time you search it will
|
61 |
|
|
go back further in the history. If nothing is on the current line, it
|
62 |
|
|
acts just like Control-P or UpArrow.</LI>
|
63 |
|
|
<LI> Shift-DownArrow or Control-DownArrow work in the opposite direction of
|
64 |
|
|
Shift-UpArrow and Control-DownArrow. </LI>
|
65 |
|
|
</UL>
|
66 |
|
|
|
67 |
|
|
<BR>
|
68 |
|
|
|
69 |
|
|
<H4><A NAME="display_hlp">Getting Help</A></H4>
|
70 |
|
|
The Console Window has its own online help system. To access the help system, enter
|
71 |
|
|
"help" at the prompt and follow the on-screen instructions. For more help, please
|
72 |
|
|
consult the <!-- What is this really called? --> <I>GDB User's Guide</I>.
|
73 |
|
|
</BODY>
|
74 |
|
|
</HTML>
|