Mercurial > emacs
changeset 72227:ae7cfda9e821
(GDB Graphical Interface): Shorten node names.
(GDB-UI Layout): Use GDB-related.
(Stack Buffer): Simplify English.
author | Nick Roberts <nickrob@snap.net.nz> |
---|---|
date | Tue, 01 Aug 2006 06:50:51 +0000 |
parents | 8e59824f44f3 |
children | a2c9b7f64744 |
files | man/building.texi |
diffstat | 1 files changed, 10 insertions(+), 11 deletions(-) [+] |
line wrap: on
line diff
--- a/man/building.texi Tue Aug 01 06:50:28 2006 +0000 +++ b/man/building.texi Tue Aug 01 06:50:51 2006 +0000 @@ -833,17 +833,17 @@ that way, you can use @kbd{M-x gdba} to invoke GDB in graphical mode. @menu -* GDB User Interface Layout:: Control the number of displayed buffers. +* GDB-UI Layout:: Control the number of displayed buffers. * Source Buffers:: Use the mouse in the fringe/margin to control your program. * Breakpoints Buffer:: A breakpoint control panel. * Stack Buffer:: Select a frame from the call stack. -* Other GDB User Interface Buffers:: Input/output, locals, registers, +* Other GDB-UI Buffers:: Input/output, locals, registers, assembler, threads and memory buffers. * Watch Expressions:: Monitor variable values in the speedbar. @end menu -@node GDB User Interface Layout +@node GDB-UI Layout @subsubsection GDB User Interface Layout @cindex GDB User Interface layout @@ -884,7 +884,7 @@ containing just the GUD buffer and a source file, type @kbd{M-x gdb-many-windows}. - You may also specify additional GUD-related buffers to display, + You may also specify additional GDB-related buffers to display, either in the same frame or a different one. Select the buffers you want with the @samp{GUD->GDB-windows} and @samp{GUD->GDB-Frames} sub-menus. If the menu-bar is unavailable, type @code{M-x @@ -1008,21 +1008,20 @@ selecting a stack frame updates it to display the local variables of the new frame. -@node Other GDB User Interface Buffers +@node Other GDB-UI Buffers @subsubsection Other Buffers @table @asis @item Input/Output Buffer @vindex gdb-use-separate-io-buffer If the variable @code{gdb-use-separate-io-buffer} is non-@code{nil}, -the executable program that is being debugged takes its input and -displays its output here. Otherwise it uses the GUD buffer for that. -To toggle whether GUD mode uses this buffer, do @kbd{M-x -gdb-use-separate-io-buffer}. That takes effect when you next -restart the program you are debugging. +the program being debugged takes its input and displays its output +here. Otherwise it uses the GUD buffer for that. To toggle whether +GUD mode uses this buffer, do @kbd{M-x gdb-use-separate-io-buffer}. +That takes effect when you next restart the program you are debugging. The history and replay commands from Shell mode are available here, -as are the commands to send signals to the program you are debugging. +as are the commands to send signals to the debugged program. @xref{Shell Mode}. @item Locals Buffer