HP gnu source-level debugger 5992-4701 User Manual
Page 29

print routines so as to allow Epoch to display values of
expressions in a separate window.
-annotate level
This option sets the annotation level inside GDB. Its effect
is identical to using `set annotate level' (see
). Annotation level controls how
much information does GDB print together with its
prompt, values of expressions, source lines, and other
types of output. Level 0 is the normal, level 1 is for use
when GDB is run as a subprocess of GNU Emacs, level 2
is the maximum annotation suitable for programs that
control GDB.
-async
Use the asynchronous event loop for the command-line
interface. GDB processes all events, such as user
1
keyboard input, via a special event loop. This allows
GDB to accept and process user commands in parallel
with the debugged process being run
1
, so you do not
need to wait for control to return to GDB before you type
the next command.
NOTE:
As of version 5.0, the target side of the
asynchronous operation is not yet in place, so '-async'
does not work fully yet.
When the standard input is connected to a terminal
device, GDB uses the asynchronous event loop by
default, unless disabled by the '-noasync' option.
-noasync
Disable the asynchronous event loop for the
command-line interface.
-baud bps
, -b bps
Set the line speed (baud rate or bits per second) of any
serial interface used by GDB for remote debugging.
-tty device
, -t device Run using device for your program's standard input and
output.
-tui
Use a Terminal User Interface. For information, use your
Web browser to read the file 'tui.html', which is
usually installed in the directory /opt/langtools/
wdb/doc
on HP-UX systems. Do not use this option if
you run GDB from Emacs (see
).
-xdb
Run in XDB compatibility mode, allowing the use of
certain XDB commands. For information, see the file
1. GDB built with DJGPP tools for MS-DOS/MS-Windows supports this mode of operation, but the event
loop is suspended when the debug target runs.
2.1 Invoking GDB
29