[Emacs-diffs] emacs/doc/emacs ChangeLog building.texi emacs.texi

[Dmitry Dzhus]

CVSROOT:        /sources/emacs
Module name:    emacs
Changes by:     Dmitry Dzhus <sphinx>   09/08/08 17:00:53

Modified files:
        doc/emacs      : ChangeLog building.texi emacs.texi 

Log message:
        * emacs.texi (Top): Add new menu items for GDB-UI.
        
        * building.texi (GDB Graphical Interface): Add Multithreaded debugging
        section. Threads buffer is in separate section now.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/emacs/doc/emacs/ChangeLog?cvsroot=emacs&r1=1.353&r2=1.354
http://cvs.savannah.gnu.org/viewcvs/emacs/doc/emacs/building.texi?cvsroot=emacs&r1=1.22&r2=1.23
http://cvs.savannah.gnu.org/viewcvs/emacs/doc/emacs/emacs.texi?cvsroot=emacs&r1=1.50&r2=1.51

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/emacs/emacs/doc/emacs/ChangeLog,v
retrieving revision 1.353
retrieving revision 1.354
diff -u -b -r1.353 -r1.354
--- ChangeLog   8 Aug 2009 02:24:57 -0000       1.353
+++ ChangeLog   8 Aug 2009 17:00:52 -0000       1.354
@@ -1,3 +1,10 @@
+2009-08-08  Dmitry Dzhus  <address@hidden>
+
+       * emacs.texi (Top): Add new menu items for GDB-UI.
+
+       * building.texi (GDB Graphical Interface): Add Multithreaded debugging
+       section. Threads buffer is in separate section now.
+
 2009-08-08  Glenn Morris  <address@hidden>
 
        * ack.texi (Acknowledgments):

Index: building.texi
===================================================================
RCS file: /sources/emacs/emacs/doc/emacs/building.texi,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- building.texi       28 Jul 2009 15:27:44 -0000      1.22
+++ building.texi       8 Aug 2009 17:00:52 -0000       1.23
@@ -854,10 +854,12 @@
 * Source Buffers::              Use the mouse in the fringe/margin to
                                 control your program.
 * Breakpoints Buffer::          A breakpoint control panel.
+* Threads Buffer::              Displays your threads.
 * Stack Buffer::                Select a frame from the call stack.
 * Other GDB-UI Buffers::        Input/output, locals, registers,
                                 assembler, threads and memory buffers.
 * Watch Expressions::           Monitor variable values in the speedbar.
+* Multithreaded Debugging::     Debugging programs with several threads.
 @end menu
 
 @node GDB-UI Layout
@@ -882,7 +884,7 @@
 |--------------------------------+--------------------------------+
 |   Primary Source buffer        |   I/O buffer for debugged pgm  |
 |--------------------------------+--------------------------------+
-|   Stack buffer                 |   Breakpoints/thread buffer    |
+|   Stack buffer                 |   Breakpoints/Thread buffer    |
 +--------------------------------+--------------------------------+
 @end group
 @end smallexample
@@ -903,7 +905,7 @@
 
   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}
+want with the @samp{GUD->GDB-Windows} and @samp{GUD->GDB-Frames}
 sub-menus.  If the menu-bar is unavailable, type @code{M-x
 address@hidden or @code{M-x
 address@hidden respectively, where
@@ -1010,10 +1012,50 @@
 Visit the source line for the breakpoint you click on.
 @end table
 
address@hidden gdb-show-threads-by-default
 When @code{gdb-many-windows} is address@hidden, the breakpoints buffer
 shares its window with the threads buffer.  To switch from one to the
-other click with @kbd{mouse-1} on the relevant button in the header
-line.
+other click with @kbd{Mouse-1} on the relevant button in the header
+line, or press @kbd{TAB} inside that buffer.  When
address@hidden is address@hidden, threads buffer
+is shown in place of breakpoints buffer by default.
+
address@hidden Threads Buffer
address@hidden Threads Buffer
+
address@hidden gdb-select-thread
+The threads buffer displays a summary of all threads currently in your
+program (@pxref{Threads, Threads, Debugging programs with multiple
+threads, gdb, The GNU debugger}).  Move point to any thread in the list
+and press @key{RET} to select it (@code{gdb-select-thread}) and
+display the associated source in the primary source buffer.
+Alternatively, click @kbd{Mouse-2} on a thread to select it.  Contents
+of all GDB buffers are updated whenever you select a thread.
+
+  You can customize variables under @code{gdb-buffers} group to select
+fields included in threads buffer.
+
address@hidden @code
address@hidden gdb-thread-buffer-verbose-names
address@hidden gdb-thread-buffer-verbose-names
+Show long thread names like @samp{Thread 0x4e2ab70 (LWP 1983)} in
+threads buffer.
+
address@hidden gdb-thread-buffer-arguments
address@hidden gdb-thread-buffer-arguments
+Show arguments of thread top frames in threads buffer.
+
address@hidden gdb-thread-buffer-locations
address@hidden gdb-thread-buffer-locations
+Show file information or library names in threads buffer.
+
address@hidden gdb-thread-buffer-addresses
address@hidden gdb-thread-buffer-addresses
+Show addresses for thread frames in threads buffer.
address@hidden table
+
+  Several other commands are available in threads buffer to assist in
+  debugging multithreaded programs (@pxref{Multithreaded Debugging}).
 
 @node Stack Buffer
 @subsubsection Stack Buffer
@@ -1069,27 +1111,12 @@
 press @key{SPC} to toggle the display of floating point registers
 (@code{toggle-gdb-all-registers}).
 
address@hidden Assembler Buffer
-The assembler buffer displays the current frame as machine code.  An
address@hidden Disassembly Buffer
+The disassembly buffer displays the current frame as machine code.  An
 arrow points to the current instruction, and you can set and remove
 breakpoints as in a source buffer.  Breakpoint icons also appear in
 the fringe or margin.
 
address@hidden Threads Buffer
address@hidden gdb-threads-select
-The threads buffer displays a summary of all threads currently in your
-program (@pxref{Threads, Threads, Debugging programs with multiple
-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
-display the associated source in the primary source buffer.
-Alternatively, click @kbd{Mouse-2} on a thread to select it.  If the
-locals buffer is visible, its contents update to display the variables
-that are local in the new thread.
-
-When there is more than one main thread and the threads buffer is
-present, Emacs displays the selected thread number in the mode line of
-many of the GDB-UI Buffers.
-
 @item Memory Buffer
 The memory buffer lets you examine sections of program memory
 (@pxref{Memory, Memory, Examining memory, gdb, The GNU debugger}).
@@ -1103,7 +1130,8 @@
 When @code{gdb-many-windows} is address@hidden, the threads buffer
 shares its window with the breakpoints buffer, and the locals buffer
 with the registers buffer.  To switch from one to the other click with
address@hidden on the relevant button in the header line.
address@hidden on the relevant button in the header line or press
address@hidden inside the buffer.
 
 @node Watch Expressions
 @subsubsection Watch Expressions
@@ -1171,6 +1199,151 @@
 address@hidden  This can be useful if you are debugging with a full
 screen Emacs frame.
 
address@hidden Multithreaded Debugging
address@hidden Multithreaded Debugging
address@hidden Multithreaded debugging in GDB
+
+  Features described in this node are supported only by GDB 7.0.
+
address@hidden Non-stop Debugging
address@hidden Non-stop debugging in GDB
+
+  For some multithreaded targets, GDB allows debugging in
address@hidden mode}.  If non-stop mode is activated, when one thread
+stops, the rest continue to execute, as opposed to traditional
address@hidden mode}, in which stopping of one thread causes @emph{all}
+threads to stop. @xref{Non-Stop Mode, , Non-Stop Mode, gdb, The GNU
+debugger}.
+
address@hidden gdb-non-stop-setting
+To activate non-stop debugging in Emacs, set
address@hidden variable to address@hidden  Note that GDB
+debugging session needs to be restarted for change of this setting to
+take effect.
+
address@hidden gdb-switch-when-another-stopped
+When a thread stops in non-stop mode, Emacs automatically switches to
+that thread.  It may be undesirable to allow switching of current
+thread when some other stopped thread is already selected.  Set
address@hidden to @code{nil} to prevent this.
+
address@hidden gdb-switch-reasons
+Emacs can decide whether or not to switch to stopped thread depending
+on the reason which caused the stop.  Customize
address@hidden to select stop reasons which make Emacs
+switch thread.
+
address@hidden gdb-stopped-hooks
address@hidden hook variable allows you to execute your
+functions whenever some thread stops.
+
+  In non-stop mode, you can switch between different modes for GUD
+execution control commands.
+
address@hidden gdb-gud-control-all-threads
address@hidden @dfn
address@hidden Non-stop/A
+
+When @code{gdb-gud-control-all-threads} is @code{t} (that’s default),
+interruption & continuation commands apply to all threads, so you can
+halt or continue all your threads with one command
+(@code{gud-stop-subjob} and @code{gud-cont}, respectively).  @samp{Go}
+button is shown on the toolbar when at least one thread is stopped,
+whereas @samp{Stop} button is shown when at least one thread is
+running.
+
address@hidden Non-stop/T
+
+When @code{gdb-gud-control-all-threads} is @code{nil}, only current
+thread is stopped/continued.  @samp{Go} and @samp{Stop} buttons on
+the GUD toolbar are shown depending on the state of current thread.
address@hidden table
+
+You can change the current value of @code{gdb-gud-control-all-threads}
+from @samp{GUD->GDB-MI} menu.
+
+  Stepping commands always apply to current thread.
+
address@hidden Observing Several Threads Simultaneously
address@hidden Observing several threads simultaneously in GDB
+
+  It’s possible to observe information for several threads
+simultaneously (in addition to buffers which show information for
+currently selected thread) using the following keys from the threads
+buffer.
+
address@hidden @key
address@hidden d
address@hidden d @r{(GDB threads buffer)}
address@hidden gdb-display-disassembly-for-thread
+Display disassembly buffer for the thread at current line.
+(@code{gdb-display-disassembly-for-thread})
+
address@hidden f
address@hidden f @r{(GDB threads buffer)}
address@hidden gdb-display-stack-for-thread
+Display stack buffer for the thread at current line.
+(@code{gdb-display-stack-for-thread}).
+
address@hidden l
address@hidden l @r{(GDB threads buffer)}
address@hidden gdb-display-locals-for-thread
+Display locals buffer for the thread at current line.
+(@code{gdb-display-locals-for-thread}).
+
address@hidden r
address@hidden r @r{(GDB threads buffer)}
address@hidden gdb-display-registers-for-thread
+Display registers buffer for the thread at current line.
+(@code{gdb-display-registers-for-thread}).
+
address@hidden D
address@hidden D @r{(GDB threads buffer)}
address@hidden gdb-frame-disassembly-for-thread
+Display a new frame with disassembly buffer for the thread at current
+line. (@code{gdb-frame-disassembly-for-thread}).
+
address@hidden F
address@hidden F @r{(GDB threads buffer)}
address@hidden gdb-frame-stack-for-thread
+Display a new frame with stack buffer for the thread at current line.
+(@code{gdb-frame-stack-for-thread}).
+
address@hidden L
address@hidden L @r{(GDB threads buffer)}
address@hidden gdb-frame-locals-for-thread
+Display a new frame with locals buffer for the thread at current line.
+(@code{gdb-frame-locals-for-thread}).
+
address@hidden R
address@hidden R @r{(GDB threads buffer)}
address@hidden gdb-frame-registers-for-thread
+Display a new frame with registers buffer for the thread at current
+line. (@code{gdb-frame-registers-for-thread}).
address@hidden table
+
+  When you create a buffer showing information about some specific
+thread, it becomes bound to that thread and keeps showing actual
+information while you debug your program.  Every GDB buffer contains a
+number of thread it shows information for in its mode name.  Thread
+number is also included in the buffer name of bound buffers to prevent
+buffer names clashing.
+
address@hidden Fine Thread Control
+
+  In non-stop mode, you can interrupt/continue your threads without
+selecting them.  Hitting @key{i} in threads buffer interrupts thread
+under point, @key{c} continues it, @key{s} steps through.  More such
+commands may be added in the future.
+
+Combined with creating bound buffers for any thread, this allows you
+to change and track state of many threads in the same time.
+
+  Note that when you interrupt a thread, it stops with @samp{signal
+received} reason.  If that reason is included in your
address@hidden (it is by default), Emacs will switch to
+that thread.
+
 @node Executing Lisp
 @section Executing Lisp Expressions
 

Index: emacs.texi
===================================================================
RCS file: /sources/emacs/emacs/doc/emacs/emacs.texi,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -b -r1.50 -r1.51
--- emacs.texi  8 Aug 2009 02:24:57 -0000       1.50
+++ emacs.texi  8 Aug 2009 17:00:53 -0000       1.51
@@ -748,10 +748,12 @@
 * Source Buffers::      Use the mouse in the fringe/margin to
                           control your program.
 * Breakpoints Buffer::  A breakpoint control panel.
+* Threads Buffer::              Displays your threads.
 * Stack Buffer::        Select a frame from the call stack.
-* Other GDB-UI 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.
+* Multithreaded Debugging::     Debugging programs with several threads.
 
 Maintaining Large Programs