# HG changeset patch
# User Eli Zaretskii <eliz@gnu.org>
# Date 1293273316 -7200
# Node ID 9b34017f06c6638b8853c694f7653a5cd00f9336
# Parent  9546b9e764b9eb2a8bac7b7131e9a22263e40740
Fix bug #7667: mention debug-on-quit in the manual.

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

diff -r 9546b9e764b9 -r 9b34017f06c6 doc/emacs/ChangeLog
--- a/doc/emacs/ChangeLog	Sat Dec 25 12:14:48 2010 +0200
+++ b/doc/emacs/ChangeLog	Sat Dec 25 12:35:16 2010 +0200
@@ -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 -r 9546b9e764b9 -r 9b34017f06c6 doc/emacs/trouble.texi
--- a/doc/emacs/trouble.texi	Sat Dec 25 12:14:48 2010 +0200
+++ b/doc/emacs/trouble.texi	Sat Dec 25 12:35:16 2010 +0200
@@ -806,6 +806,13 @@
 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