Mercurial > emacs
changeset 38130:7aad2fda759d
Update how to find etc/DEBUG.
Clarify what to do instead of finding more examples of a bug.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Wed, 20 Jun 2001 10:49:08 +0000 |
parents | 2db5f7aaa215 |
children | a678d1512bf0 |
files | man/trouble.texi |
diffstat | 1 files changed, 7 insertions(+), 8 deletions(-) [+] |
line wrap: on
line diff
--- a/man/trouble.texi Wed Jun 20 10:47:48 2001 +0000 +++ b/man/trouble.texi Wed Jun 20 10:49:08 2001 +0000 @@ -819,11 +819,8 @@ 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 @@ 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