From 649f602cd69fb97e9572f526043e288ab9f34024 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Sat, 4 Feb 2012 19:37:19 -0800 Subject: [PATCH] More doc for debug-on-event. * emacs/trouble.texi (Checklist): Mention debug-on-event. * lispref/debugging.texi (Error Debugging): Mention debug-on-event default. --- doc/emacs/ChangeLog | 2 ++ doc/emacs/trouble.texi | 6 ++++++ doc/lispref/ChangeLog | 4 ++++ doc/lispref/debugging.texi | 4 ++-- 4 files changed, 14 insertions(+), 2 deletions(-) diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog index 6ff188a3da..ab4161c75b 100644 --- a/doc/emacs/ChangeLog +++ b/doc/emacs/ChangeLog @@ -1,5 +1,7 @@ 2012-02-05 Glenn Morris + * trouble.texi (Checklist): Mention debug-on-event. + * maintaining.texi (Maintaining): Add cross-ref to ERT. 2012-02-04 Glenn Morris diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi index 8cb5ab44a2..6c6dbea952 100644 --- a/doc/emacs/trouble.texi +++ b/doc/emacs/trouble.texi @@ -784,6 +784,12 @@ 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. +@vindex debug-on-event +If you cannot get Emacs to respond to @kbd{C-g} (e.g., because +@code{inhibit-quit} is set), then you can try sending the signal +specified by @code{debug-on-event} (default SIGUSR2) from outside +Emacs to cause it to enter the debugger. + @item Check whether any programs you have loaded into the Lisp world, including your initialization file, set any variables that may affect diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index 681b9b5467..65740feeee 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,7 @@ +2012-02-05 Glenn Morris + + * debugging.texi (Error Debugging): Mention debug-on-event default. + 2012-02-04 Glenn Morris * backups.texi (Reverting): Mention revert-buffer-in-progress-p. diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi index a17fc60718..cc92fc225f 100644 --- a/doc/lispref/debugging.texi +++ b/doc/lispref/debugging.texi @@ -153,8 +153,8 @@ If you set @code{debug-on-event} to a special event (@pxref{Special Events}), Emacs will try to enter the debugger as soon as it receives this event, bypassing @code{special-event-map}. At present, the only supported values correspond to the signals @code{SIGUSR1} and -@code{SIGUSR2}. This can be helpful when @code{inhibit-quit} is set -and Emacs is not otherwise responding. +@code{SIGUSR2} (this is the default). This can be helpful when +@code{inhibit-quit} is set and Emacs is not otherwise responding. @end defopt To debug an error that happens during loading of the init -- 2.20.1