Doc fix for gdb-stopped-functions.

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

2 files changed, 7 insertions, 2 deletions

diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index 4591cfb99fe..45d4377f34a 100644
--- 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 3a3630138de..e0ea72902fb 100644
--- 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