gdb.info: Mode Options
Go backward to File Options
Go up to Invoking GDB
Go to the top op gdb
You can run GDB in various alternative modes--for example, in batch
mode or quiet mode.
Do not execute commands found in any initialization files.
Normally, GDB executes the commands in these files after all the
command options and arguments have been processed. *Note Command
files: Command Files.
"Quiet". Do not print the introductory and copyright messages.
These messages are also suppressed in batch mode.
Run in batch mode. Exit with status `0' after processing all the
command files specified with `-x' (and all commands from
initialization files, if not inhibited with `-n'). Exit with
nonzero status if an error occurs in executing the GDB commands in
the command files.
Batch mode may be useful for running GDB as a filter, for example
to download and run a program on another computer; in order to
make this more useful, the message
Program exited normally.
(which is ordinarily issued whenever a program running under GDB
control terminates) is not issued when running in batch mode.
"No windows". If GDB comes with a graphical user interface (GUI)
built in, then this option tells GDB to only use the command-line
interface. If no GUI is available, this option has no effect.
If GDB includes a GUI, then this option requires it to be used if
Run GDB using DIRECTORY as its working directory, instead of the
GNU Emacs sets this option when it runs GDB as a subprocess. It
tells GDB to output the full file name and line number in a
standard, recognizable fashion each time a stack frame is
displayed (which includes each time your program stops). This
recognizable format looks like two `\032' characters, followed by
the file name, line number and character position separated by
colons, and a newline. The Emacs-to-GDB interface program uses
the two `\032' characters as a signal to display the source code
for the frame.
The Epoch Emacs-GDB interface sets this option when it runs GDB as
a subprocess. It tells GDB to modify its print routines so as to
allow Epoch to display values of expressions in a separate window.
This option sets the "annotation level" inside GDB. Its effect is
identical to using `set annotate LEVEL' (*note Annotations::).
The annotation LEVEL controls how much information GDB prints
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 3 is the
maximum annotation suitable for programs that control GDB, and
level 2 has been deprecated.
The annotation mechanism has largely been superseeded by GDB/MI
Change interpretation of command line so that arguments following
the executable file are passed as command line arguments to the
inferior. This option stops option processing.
Set the line speed (baud rate or bits per second) of any serial
interface used by GDB for remote debugging.
Run using DEVICE for your program's standard input and output.
Activate the "Text User Interface" when starting. The Text User
Interface manages several text windows on the terminal, showing
source, assembly, registers and GDB command outputs (*note GDB
Text User Interface: TUI.). Alternatively, the Text User
Interface can be enabled by invoking the program `gdbtui'. Do not
use this option if you run GDB from Emacs (*note Using GDB under
GNU Emacs: Emacs.).
Use the interpreter INTERP for interface with the controlling
program or device. This option is meant to be set by programs
which communicate with GDB using it as a back end. *Note Command
`--interpreter=mi' (or `--interpreter=mi2') causes GDB to use the
"GDB/MI interface" (*note The GDB/MI Interface: GDB/MI.) included
since GDBN version 6.0. The previous GDB/MI interface, included
in GDB version 5.3 and selected with `--interpreter=mi1', is
deprecated. Earlier GDB/MI interfaces are no longer supported.
Open the executable and core files for both reading and writing.
This is equivalent to the `set write on' command inside GDB (*note
This option causes GDB to print statistics about time and memory
usage after it completes each command and returns to the prompt.
This option causes GDB to print its version number and no-warranty
blurb, and exit.
Created Mon Nov 8 17:42:35 2004 on tillpc with info_to_html version 0.9.6.