Index: lisp/progmodes/gdb-ui.el
===================================================================
RCS file: /sources/emacs/emacs/lisp/progmodes/gdb-ui.el,v
retrieving revision 1.191
diff -c -r1.191 gdb-ui.el
*** lisp/progmodes/gdb-ui.el	10 Nov 2006 09:38:11 -0000	1.191
--- lisp/progmodes/gdb-ui.el	25 Nov 2006 13:19:16 -0000
***************
*** 214,220 ****
  
  ;;;###autoload
  (defun gdba (command-line)
!   "Run gdb on program FILE in buffer *gud-FILE*.
  The directory containing FILE becomes the initial working directory
  and source-file directory for your debugger.
  
--- 214,220 ----
  
  ;;;###autoload
  (defun gdba (command-line)
!   "Run gdb in GUI mode on program FILE in buffer *gud-FILE*.
  The directory containing FILE becomes the initial working directory
  and source-file directory for your debugger.
  
Index: lisp/progmodes/gud.el
===================================================================
RCS file: /sources/emacs/emacs/lisp/progmodes/gud.el,v
retrieving revision 1.116
diff -c -r1.116 gud.el
*** lisp/progmodes/gud.el	5 Sep 2006 03:40:54 -0000	1.116
--- lisp/progmodes/gud.el	25 Nov 2006 13:19:19 -0000
***************
*** 680,687 ****
  default this command starts GDB using a graphical interface.  See
  `gdba' for more information.
  
! To run GDB in text command mode, set `gud-gdb-command-name' to
! \"gdb --fullname\" and include the pathname, if necessary."
    (interactive (list (gud-query-cmdline 'gdb)))
  
    (if (and gud-comint-buffer
--- 680,687 ----
  default this command starts GDB using a graphical interface.  See
  `gdba' for more information.
  
! To run GDB in text command mode, delete \"--annotate=3\" from
! `gud-gdb-command-name', and add \"--fullname\"."
    (interactive (list (gud-query-cmdline 'gdb)))
  
    (if (and gud-comint-buffer
Index: man/building.texi
===================================================================
RCS file: /sources/emacs/emacs/man/building.texi,v
retrieving revision 1.109
diff -c -r1.109 building.texi
*** man/building.texi	7 Oct 2006 23:38:51 -0000	1.109
--- man/building.texi	25 Nov 2006 13:19:21 -0000
***************
*** 536,545 ****
  @subsection Debugger Operation
  
  @cindex fringes, and current execution line in GUD
!   When you run a debugger with GUD using the textual interface, the
! debugger uses an Emacs buffer for its ordinary input and output.  This
! is called the GUD buffer.  Input and output from the program you are
! debugging also use this buffer.
  
    The debugger displays the source files of the program by visiting
  them in Emacs buffers.  An arrow in the left fringe indicates the
--- 536,545 ----
  @subsection Debugger Operation
  
  @cindex fringes, and current execution line in GUD
!   When you run a debugger with GUD, the debugger uses an Emacs buffer
! for its ordinary input and output. This is called the GUD buffer.
! Input and output from the program you are debugging also use this
! buffer.
  
    The debugger displays the source files of the program by visiting
  them in Emacs buffers.  An arrow in the left fringe indicates the
***************
*** 815,838 ****
  
    By default, the command @code{gdb} starts GDB using a graphical
  interface, using Emacs windows for display program state information.
! In effect, this makes Emacs into an IDE (interactive development
! environment).  With it, you do not need to use textual GDB commands;
! you can control the debugging session with the mouse.  For example,
! you can click in the fringe of a source buffer to set a breakpoint
! there, or on a stack frame in the stack buffer to select that frame.
! 
!   This mode requires telling GDB that its ``screen size'' is
! unlimited, so it sets the height and width accordingly.  For correct
! 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, set @code{gud-gdb-command-name} to @code{"gdb --fullname"} or
! edit the startup command in the minibuffer to say that.  You need to
! do use text command mode to run multiple debugging sessions within one
! Emacs session.  If you have customized @code{gud-gdb-command-name} in
! that way, you can use @kbd{M-x gdba} to invoke GDB in graphical mode.
  
  @menu
  * GDB-UI Layout::               Control the number of displayed buffers.
--- 815,856 ----
  
    By default, the command @code{gdb} starts GDB using a graphical
  interface, using Emacs windows for display program state information.
! This is called ``GUI mode''. In effect, this makes Emacs into an IDE
! (interactive development environment). With it, you do not need to use
! textual GDB commands; you can control the debugging session with the
! mouse. For example, you can click in the fringe of a source buffer to
! set a breakpoint there, or on a stack frame in the stack buffer to
! select that frame.
! 
!   To display the program state information windows, you must set the
! variable @code{gdb-many-windows} to non-@code{nil}. Or you can use the
! command @code{gdba} to start the debugger.
! 
!   You can also run GDB without the program state information windows;
! this also disables many of the mouse bindings that interact with the
! debugger. This is called ``text command mode''. 
! 
!   You need to use text mode for the first and subsequent debugging
! sessions if you plan to run multiple debugging sessions within one
! Emacs session.
  
  @vindex gud-gdb-command-name
  @findex gdba
!   Emacs automatically switches to GUI mode if it sees annotations in
! the gdb output. GDB generates annotations when started with the
! command line option @code{"--annotate=3"}, which is set by default in
! @code{gud-gdb-command-name}. To run in text mode, you must customize
! @code{gud-gdb-command-name} to delete this option, and specify
! @code{"--fullname"} instead. Or you can make this change in the
! startup command in the minibuffer.
! 
! If you have customized @code{gud-gdb-command-name} in that way, you
! can use @code{gdba} to invoke GDB in graphical mode; it uses the
! default command @code{gud-gdba-command-name}.
! 
!   GUI mode requires telling GDB that its ``screen size'' is unlimited,
! so it sets the height and width accordingly. For correct operation you
! must not change these values during the GDB session.
  
  @menu
  * GDB-UI Layout::               Control the number of displayed buffers.