14
Chapter 4. Getting In and Out of gdb
-quiet
-silent
-q
"Quiet". Do not print the introductory and copyright messages. These messages are also sup-
pressed in batch mode.
-batch
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.
-nowindows
-nw
"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.
-windows
-w
If gdb includes a GUI, then this option requires it to be used if possible.
-cd
directory
Run gdb using
directory
as its working directory, instead of the current directory.
-fullname
-f
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.
-epoch
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.
-annotate
level
This option sets the
annotation level
inside gdb. Its effect is identical to using
set annotate
level
(refer to Chapter 27
gdb Annotations
). 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.
Summary of Contents for ENTERPRISE LINUX 4 - DEVELOPER TOOLS GUIDE
Page 1: ...Red Hat Enterprise Linux 4 Debugging with gdb ...
Page 12: ...2 Chapter 1 Debugging with gdb ...
Page 28: ...18 Chapter 4 Getting In and Out of gdb ...
Page 34: ...24 Chapter 5 gdb Commands ...
Page 44: ...34 Chapter 6 Running Programs Under gdb ...
Page 68: ...58 Chapter 8 Examining the Stack ...
Page 98: ...88 Chapter 10 Examining Data ...
Page 112: ...102 Chapter 12 Tracepoints ...
Page 118: ...108 Chapter 13 Debugging Programs That Use Overlays ...
Page 138: ...128 Chapter 14 Using gdb with Different Languages ...
Page 144: ...134 Chapter 15 Examining the Symbol Table ...
Page 170: ...160 Chapter 19 Debugging remote programs ...
Page 198: ...188 Chapter 21 Controlling gdb ...
Page 204: ...194 Chapter 22 Canned Sequences of Commands ...
Page 206: ...196 Chapter 23 Command Interpreters ...
Page 216: ...206 Chapter 25 Using gdb under gnu Emacs ...
Page 296: ...286 Chapter 27 gdb Annotations ...
Page 300: ...290 Chapter 28 Reporting Bugs in gdb ...
Page 322: ...312 Chapter 30 Using History Interactively ...
Page 362: ...352 Appendix D gdb Remote Serial Protocol ...
Page 380: ...370 Appendix F GNU GENERAL PUBLIC LICENSE ...
Page 386: ...376 Appendix G GNU Free Documentation License ...
Page 410: ......