Changeset 4140 for trunk/man/building.texi

Timestamp:

08/10/06 11:19:54 (2 years ago)

Author:

miyoshi

Message:

Sync up with Emacs CVS HEAD.

Files:

• trunk/man/building.texi (modified) (10 diffs)

trunk/man/building.texi

@@ -834 +834 @@
-
-@menu
-
+
+
+
-* Breakpoints Buffer::          A breakpoint control panel.
-* Stack Buffer::                Select a frame from the call stack.
- User Interface Buffers::
+-UI Buffers::       
-                                assembler, threads and memory buffers.
-* GDB commands in the Fringe::  Use the mouse in the fringe/margin to
-                                control your program.
-* Watch Expressions::           Monitor variable values in the speedbar.
-@end menu
-
- User Interface
+-UI
-@subsubsection GDB User Interface Layout
-@cindex GDB User Interface layout
@@ -864 +864 @@
-|   GUD buffer (I/O of GDB)      |   Locals buffer                |
-|--------------------------------+--------------------------------+
-Source buffer        
+Primary Source buffer
-|--------------------------------+--------------------------------+
-|   Stack buffer                 |   Breakpoints buffer           |
@@ -872 +872 @@
-
-  However, if @code{gdb-use-separate-io-buffer} is @code{nil}, the I/O
-source buffer occupies the full width
-
+primary source buffer occupies the full
+width 
-
-@findex gdb-restore-windows
@@ -885 +885 @@
-gdb-many-windows}.
-
-UD
+DB
-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}
@@ -905 +905 @@
-places.
-
+@node Source Buffers
+@subsubsection Source Buffers
+@cindex GDB commands in Fringe
+
+@c @findex gdb-mouse-set-clear-breakpoint
+@c @findex gdb-mouse-toggle-breakpoint
+Many GDB commands can be entered using keybindings or the tool bar but
+sometimes it is quicker to use the fringe.  These commands either
+manipulate breakpoints or control program execution.  When there is no
+fringe, you can use the margin but this is only present when the
+source file already has a breakpoint.
+
+You can click @kbd{Mouse-1} in the fringe or display margin of a
+source buffer to set a breakpoint there and, on a graphical display, a
+red bullet will appear on that line.  If a breakpoint already exists
+on that line, the same click will remove it.  You can also enable or
+disable a breakpoint by clicking @kbd{C-Mouse-1} on the bullet.
+
+A solid arrow in the left fringe of a source buffer indicates the line
+of the innermost frame where the debugged program has stopped. A
+hollow arrow indicates the current execution line of higher level
+frames.
+
+If you drag the arrow in the fringe with @kbd{Mouse-1}
+(@code{gdb-mouse-until}), execution will continue to the line where
+you release the button, provided it is still in the same frame.
+Alternatively, you can click @kbd{Mouse-3} at some point in the fringe
+of this buffer and execution will advance to there.  A similar command
+(@code{gdb-mouse-jump}) allows you to jump to a source line without
+executing the intermediate lines by clicking @kbd{C-Mouse-3}.  This
+command allows you to go backwards which can be useful for running
+through code that has already executed, in order to examine its
+execution in more detail.
+
+@table @kbd
+@item Mouse-1
+Set or clear a breakpoint.
+
+@item C-Mouse-1
+Enable or disable a breakpoint.
+
+@item Mouse-3
+Continue execution to here.
+
+@item C-Mouse-3
+Jump to here.
+@end table
+
+If the variable @code{gdb-find-source-frame} is non-@code{nil} and
+execution stops in a frame for which there is no source code e.g after
+an interrupt, then Emacs finds and displays the first frame further up
+stack for which there is source.  If it is @code{nil} then the source
+buffer continues to display the last frame which maybe more useful,
+for example, when re-setting a breakpoint.
+
-@node Breakpoints Buffer
-@subsubsection Breakpoints Buffer
@@ -919 +974 @@
-Enable/disable the current breakpoint (@code{gdb-toggle-breakpoint}).
-On a graphical display, this changes the color of a bullet in the
-the
+a
-the breakpoint is enabled and grey when it is disabled.  Text-only
-terminals correspondingly display a @samp{B} or @samp{b}.
@@ -954 +1009 @@
-the new frame.
-
- User Interface
+-UI
-@subsubsection Other Buffers
-
@@ -961 +1016 @@
-@vindex gdb-use-separate-io-buffer
-If the variable @code{gdb-use-separate-io-buffer} is non-@code{nil},
-
-
-
-
-
+
+
+
+
-
-The history and replay commands from Shell mode are available here,
-program you are debugging
+debugged program
-@xref{Shell Mode}.
-
@@ -1004 +1058 @@
-threads, gdb, The GNU debugger}).  Move point to any thread in the
-list and press @key{RET} to select it (@code{gdb-threads-select}) and
-source buffer.  Alternatively,
-
-
-
+primary source buffer.
+
+
+that are local 
-
-@item Memory Buffer
@@ -1016 +1070 @@
-displays.  Click @kbd{Mouse-3} on the header line to select the
-display format or unit size for these data items.
-@end table
-
-@node GDB commands in the Fringe
-@subsubsection GDB commands in the Fringe
-@cindex GDB commands in the Fringe
-
-@c @findex gdb-mouse-set-clear-breakpoint
-@c @findex gdb-mouse-toggle-breakpoint
-Many GDB commands can be entered using keybindings or the tool bar but
-sometimes it is quicker to use the fringe.  These commands either
-manipulate breakpoints or control program execution.  When there is no
-fringe, you can use the margin but this is only present when the
-source file already has a breakpoint.
-
-You can click @kbd{Mouse-1} in the fringe or display margin of a
-source buffer to set a breakpoint there and, on a graphical display, a
-red bullet will appear on that line.  If a breakpoint already exists
-on that line, the same click will remove it.  You can also enable or
-disable a breakpoint by clicking @kbd{C-Mouse-1} on the bullet.
-
-If you drag the debugger arrow in the fringe with @kbd{Mouse-1}
-(@code{gdb-mouse-until}), execution will continue to the line where
-you release the button, provided it is still in the same frame.
-Alternatively, you can click @kbd{Mouse-3} at some point in the fringe
-of this buffer and execution will advance to there.  A similar command
-(@code{gdb-mouse-jump}) allows you to jump to a source line without
-executing the intermediate lines by clicking @kbd{C-Mouse-3}.  This
-command allows you to go backwards which can be useful for running
-through code that has already executed, in order to examine its
-execution in more detail.
-
-@table @kbd
-@item Mouse-1
-Set or clear a breakpoint.
-
-@item C-Mouse-1
-Enable or disable a breakpoint.
-
-@item Mouse-3
-Continue execution to here.
-
-@item C-Mouse-3
-Jump to here.
-@end table
-