Using MDB Commands Interactively
This chapter describes the MDB interactive command line editing and history functions, the output pager, and debugger signal handling.
4.1. Command Reentry
The text of
HISTSIZE (default 128) commands entered from
a terminal device is saved in memory. The inline editing facility provides
key mappings for searching and fetching elements from the history list.
4.2. Inline Editing
If standard input is a terminal
device, MDB provides some simple emacs-style facilities for editing the command
next commands in edit mode provide access to the history list. Only
strings, not patterns, are matched when searching. In the list below, the
notation for control characters is the caret character (
followed by a character shown in uppercase. The notation for escape sequences
is M- followed by a character. For example, M-f (pronounced meta-
eff) is entered by pressing the ESC keyboard
key followed by the f key, or by pressing the Meta key
followed by the f key on keyboards that support a Meta key.
A command line is committed and executed using
NEWLINE. The edit commands are:
Move cursor forward (right) one character.
Move cursor forward one word.
Move cursor backward (left) one character.
Move cursor backward one word.
Move cursor to start of line.
Move cursor to end of line.
Delete current character, if the current line is not empty. If the current line is empty, ^D denotes EOF and the debugger will exit.
(Meta-backspace) Delete previous word.
Delete from the cursor to the end of the line.
Reprint the current line.
Transpose the current character with the next character.
Fetch the next command from the history. Each time ^N is entered, the next command forward in time is retrieved.
Fetch the previous command from the history. Each time ^P is entered, the next command backward in time is retrieved.
Search backward in the history for a previous command line containing string. The string should be terminated by a
NEWLINE. If string is omitted, the previous history element containing the most recent string is retrieved.
The editing mode also interprets the following user-defined sequences as editing commands. User-defined sequences can be read or modified using the stty(1) command.
User-defined erase character (usually ^H or ^?). Delete previous character.
User-defined interrupt character (usually ^C). Abort the current command and print a new prompt.
User-defined kill character (usually ^U). Kill the entire current command line.
User-defined quit character (usually ^\). Quit the debugger.
User-defined suspend character (usually ^Z). Suspend the debugger.
User-defined word erase character (usually ^W). Erase the preceding word.
On keyboards that
support an extended keypad with arrow keys,
these keystrokes as editing commands:
- Up arrow
Fetch the previous command from the history (same as ^P)
- Down arrow
Fetch the next command from the history (same as ^N)
- Left arrow
Move cursor backward one character (same as ^B)
- Right arrow
Move cursor forward one character (same as ^F)
4.3. Keyboard Shortcuts
MDB provides a set of keyboard shortcuts that bind individual keystrokes to common MDB commands when the keystroke listed in the table below is typed as the first character following the MDB prompt. The keyboard shortcuts are:
Execute the command
Execute the command
4.4. Output Pager
MDB provides a
built-in output pager. The output pager is enabled if the debugger's standard
output is a terminal device. Each time a command is executed,
after each screenful of output is written and displays a pager prompt:
>> More [<space>, <cr>, q, n, c, a] ?
The following key sequences are recognized by the pager:
Display the next screenful of output
- a, A
Abort the current top-level command and return to the prompt
- c, C
Continue displaying output without pausing at each screenful, until the current top-level command is complete
- n, N,
Display the next line of output
- q, Q, ^C, ^\
Quit (abort) the current dcmd only
4.5. Signal Handling
the PIPE and QUIT signals. The INT signal aborts the command that is currently
executing. The debugger intercepts and provides special handling for the ILL,
TRAP, EMT, FPE, BUS, and SEGV signals. If any of these signals is generated
asynchronously (delivered from another process using the kill(2) call), mdb restores the signal
to its default disposition and dumps core. However, if any of these signals
is generated synchronously by the debugger process itself and
a dcmd from an externally loaded
dmod is currently executing,
and standard input is a terminal,
mdb will provide a menu
of choices allowing the user to force a core dump, quit without producing
a core dump, stop for attach by a debugger, or attempt to resume. The resume
option will abort all active commands and unload the
dcmd was active at the time the fault occurred. It can then be subsequently
re-loaded by the user. The resume option provides limited protection against
buggy dcmds. Refer to Warnings, Use of
the Error Recovery Mechanism, for information about the risks associated with
the resume option.