Doc fix for gdb-stopped-functions.

* building.texi (Multithreaded Debugging): gdb-stopped-hooks is
actually named gdb-stopped-functions.

diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index 4591cfb99fec752b8a7cf5ad2c0cae24ca8efb76..45d4377f34aeda49b8e15c2e0252171486c5d160 100644 (file)
--- a/doc/emacs/ChangeLog
+++ b/doc/emacs/ChangeLog
@@ -1,3 +1,8 @@
+2012-11-12  Chong Yidong  <cyd@gnu.org>
+
+       * building.texi (Multithreaded Debugging): gdb-stopped-hooks is
+       actually named gdb-stopped-functions.
+
 2012-11-12  Glenn Morris  <rgm@gnu.org>
 
        * misc.texi (Single Shell): Mention async-shell-command-buffer.

diff --git a/doc/emacs/building.texi b/doc/emacs/building.texi
index 3a3630138de9d589765f75cd909508d2ad2c95e3..e0ea72902fbf5536fb7cec62507c0b2ca1a48e3f 100644 (file)
--- a/doc/emacs/building.texi
+++ b/doc/emacs/building.texi
@@ -1244,8 +1244,8 @@ depending on the reason which caused the stop.  Customize the variable
 @code{gdb-switch-reasons} to select the stop reasons which will cause
 a thread switch.
 
-@vindex gdb-stopped-hooks
-  The variable @code{gdb-stopped-hooks} allows you to execute your
+@vindex gdb-stopped-functions
+  The variable @code{gdb-stopped-functions} allows you to execute your
 functions whenever some thread stops.
 
   In non-stop mode, you can switch between different modes for GUD