Debugging with GDB (September 2007)

Chapter 2: Getting In and Out of GDB 15
-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 system s. Do not use this option if you
run GDB from Emacs (see see Chapter 19 [Using GDB under gnu Emacs],
page 255).
-xdb Run in XDB compatibility mode, allowing the use of certain XDB commands.
For information, see the file ‘xdb_trans.html’, which is usually installed in the
directory /opt/langtools/wdb/doc on HP-UX systems.
-interpreter interp
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. For example, ‘--interpreter=mi’ causes GDB to use
the gdbmi interface (see Chapter 21 [The gdb/mi Interface], page 265).
-write Open the executable and core files for both reading and writing. This is equiv-
alent to the ‘set write on’ command inside GDB (see Section 11.6 [Patching],
page 100).
-statistics
This option causes GDB to print statistics about time and memory usage after
it completes each command and returns to the prompt.
-version This option causes GDB to print its version number and no-warranty blurb,
and exit.
-pid This option causes GDB to attach to a running process .
-inline This option causes the debugger to start with the inline debugging on.
-src_no_g
This option is used to se t the limited source level debugging without compiling.
2.1.3 Redirecting WDB input and output to a file
To redirect WDB input and output to a file, use either of these commands to start the
debugger:
$ script log1
$ gdb
or
$ gdb | tee log1