Fix bug #7667: mention debug-on-quit in the manual.

 trouble.texi (Checklist): Mention debug-on-quit.

diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index 7fa2c1aaf76506d6583cbecb4fdc7f400809bd0e..d0ad25bb1af8e58672d1e03005ae379b863b5828 100644 (file)
--- a/doc/emacs/ChangeLog
+++ b/doc/emacs/ChangeLog
@@ -1,3 +1,7 @@
+2010-12-25  Eli Zaretskii  <eliz@gnu.org>
+
+       * trouble.texi (Checklist): Mention debug-on-quit.  (Bug#7667)
+
 2010-12-18  Glenn Morris  <rgm@gnu.org>
 
        * maintaining.texi: Move inclusion of emerge after EDE, so that it

diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi
index ef8b5ab67724c1c1657b476a3d703dd868b9aa00..b8cfd322bd4b4c455807fe4fd38ed655f387c49d 100644 (file)
--- a/doc/emacs/trouble.texi
+++ b/doc/emacs/trouble.texi
@@ -806,6 +806,13 @@ This use of the debugger is possible only if you know how to make the
 bug happen again.  If you can't make it happen again, at least copy
 the whole error message.
 
+@vindex debug-on-quit
+If Emacs appears to be stuck in an infinite loop or in a very long
+operation, typing @kbd{C-g} with the variable @code{debug-on-quit}
+non-@code{nil} will start the Lisp debugger and show a backtrace.
+This backtrace is useful for debugging such long loops, so if you can
+produce it, copy it into the bug report.
+
 @item
 Check whether any programs you have loaded into the Lisp world,
 including your @file{.emacs} file, set any variables that may affect the