# HG changeset patch
# User Nick Roberts <nickrob@snap.net.nz>
# Date 1191484481 0
# Node ID b1c01a5355f999554e45379a0190d08d99241eab
# Parent  d11b67d93bf3c200e5b554b389308543745b59c6
(GDB Graphical Interface): Remove references to gdba
and mention gud-gdb.

diff -r d11b67d93bf3 -r b1c01a5355f9 man/building.texi
--- a/man/building.texi	Thu Oct 04 07:52:55 2007 +0000
+++ b/man/building.texi	Thu Oct 04 07:54:41 2007 +0000
@@ -820,17 +820,14 @@
 operation you must not change these values during the GDB session.
 
 @vindex gud-gdb-command-name
-@findex gdba
-  You can also run GDB in text command mode, like other debuggers.  To
-do this, replace the GDB @code{"--annotate=3"} option with
-@code{"--fullname"} either in the minibuffer for the current Emacs
-session, or the custom variable @code{gud-gdb-command-name} for all
-future sessions.  You need to use text command mode to debug multiple
-programs within one Emacs session.  If you have customized
-@code{gud-gdb-command-name} in this way, you can use @kbd{M-x gdba} to
-invoke GDB in graphical mode.  Moreover, this command succeeds where
-@kbd{M-x gdb} fails, such as when your @file{.gdbinit} file contains
-executable GDB commands.
+  You can also run GDB in text command mode, like the other debuggers
+in Emacs.  To do this, replace the GDB @code{"--annotate=3"} option
+with @code{"--fullname"} either in the minibuffer for the current
+Emacs session, or the custom variable @code{gud-gdb-command-name} for
+all future sessions.  You need to use text command mode to debug
+multiple programs within one Emacs session.  You can also use
+@kbd{M-x gud-gdb} to invoke GDB in text command mode if you have
+problems before execution has started.
 
 @menu
 * GDB-UI Layout::               Control the number of displayed buffers.