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

[Nick Roberts]

CVSROOT:        /sources/emacs
Module name:    emacs
Branch:         EMACS_23_1_RC
Changes by:     Nick Roberts <nickrob>  09/08/08 04:23:52

Modified files:
        doc/emacs      : building.texi 

Log message:
        (Reverse Debugging): New section.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/emacs/doc/emacs/building.texi?cvsroot=emacs&only_with_tag=EMACS_23_1_RC&r1=1.21.2.2&r2=1.21.2.3

Patches:
Index: building.texi
===================================================================
RCS file: /sources/emacs/emacs/doc/emacs/building.texi,v
retrieving revision 1.21.2.2
retrieving revision 1.21.2.3
diff -u -b -r1.21.2.2 -r1.21.2.3
--- building.texi       28 Jul 2009 15:27:27 -0000      1.21.2.2
+++ building.texi       8 Aug 2009 04:23:52 -0000       1.21.2.3
@@ -858,6 +858,7 @@
 * Other GDB-UI Buffers::        Input/output, locals, registers,
                                 assembler, threads and memory buffers.
 * Watch Expressions::           Monitor variable values in the speedbar.
+* Reverse Debugging::           Execute and reverse debug your program.
 @end menu
 
 @node GDB-UI Layout
@@ -882,7 +883,7 @@
 |--------------------------------+--------------------------------+
 |   Primary Source buffer        |   I/O buffer for debugged pgm  |
 |--------------------------------+--------------------------------+
-|   Stack buffer                 |   Breakpoints/thread buffer    |
+|   Stack buffer                 |   Breakpoints/Threads buffer   |
 +--------------------------------+--------------------------------+
 @end group
 @end smallexample
@@ -1171,6 +1172,26 @@
 address@hidden  This can be useful if you are debugging with a full
 screen Emacs frame.
 
address@hidden Reverse Debugging
address@hidden Reverse Debugging
+
+  The GDB tool bar shares many buttons with the other GUD debuggers
+for tasks like stepping and printing expressions.  It also has a
+further set of buttons that allow reverse debugging (@pxref{Process
+Record and Replay, , ,gdb, The GNU debugger}).  This is useful when it
+takes a long time to reproduce the conditions where your program fails
+or for transient problems, like race conditions in multi-threaded
+problems, where a failure might otherwise be hard to reproduce.
+
+To use reverse debugging set a breakpoint near the location of
+interest and run your program to that point.  Process recording is
+enabled by clicking on the record button.  At this point a new set of
+buttons appear that allow execution in the reverse direction.  Execute
+over the code where the problem occurs and then use the new set of
+buttons to retrace your steps, examine values and analyse the problem.
+When analysis is complete then turn off process recording by clicking
+on the record button again.
+
 @node Executing Lisp
 @section Executing Lisp Expressions