Doc fix for gdb-stopped-functions.

* building.texi (Multithreaded Debugging): gdb-stopped-hooks is
actually named gdb-stopped-functions.
This commit is contained in:
Chong Yidong 2012-11-13 03:54:37 +08:00
parent 53f8dc8482
commit 0f5414fca8
2 changed files with 7 additions and 2 deletions

View file

@ -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.

View file

@ -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