From ac41be63eece3f125db148bc1bc4d539272c152d Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Wed, 20 Jun 2001 10:49:08 +0000 Subject: [PATCH] Update how to find etc/DEBUG. Clarify what to do instead of finding more examples of a bug. --- man/trouble.texi | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/man/trouble.texi b/man/trouble.texi index ee65d7315fe..514fa9f1a20 100644 --- a/man/trouble.texi +++ b/man/trouble.texi @@ -819,11 +819,8 @@ That file also includes instructions for investigating problems whereby Emacs stops responding (many people assume that Emacs is ``hung,'' whereas in fact it might be in an infinite loop). -In an installed Emacs, the file @file{etc/DEBUG} is in the same -directory where the Emacs on-line documentation file @file{DOC}, -typically in the @file{/usr/local/share/emacs/@var{version}/etc/} -directory. The directory for your installation is stored in the -variable @code{data-directory}. +To find the file @file{etc/DEBUG} in your Emacs installation, use the +directory name stored in the variable @code{data-directory}. @end itemize Here are some things that are not necessary in a bug report: @@ -838,9 +835,11 @@ which changes to the input file will make the bug go away and which changes will not affect it. This is often time-consuming and not very useful, because the way we -will find the bug is by running a single example under the debugger with -breakpoints, not by pure deduction from a series of examples. You might -as well save time by not searching for additional examples. +will find the bug is by running a single example under the debugger +with breakpoints, not by pure deduction from a series of examples. +You might as well save time by not searching for additional examples. +It is better to send the bug report right away, go back to editing, +and find another bug to report. Of course, if you can find a simpler example to report @emph{instead} of the original one, that is a convenience. Errors in the output will be -- 2.39.2