summaryrefslogtreecommitdiff
path: root/etc/DEBUG
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2014-07-26 16:40:53 +0300
committerEli Zaretskii <eliz@gnu.org>2014-07-26 16:40:53 +0300
commitc734f28e4345a96ab5c4f09e2821e5178ebb0cd0 (patch)
tree7385b77f304debf8d8de4e0359b508110a0c81a8 /etc/DEBUG
parente72e6612763d178bc283e8c8ec72325b85aa2384 (diff)
downloademacs-c734f28e4345a96ab5c4f09e2821e5178ebb0cd0.tar.gz
Fix bug #18113 with ambiguous wording in etc/DEBUG.
etc/DEBUG: Improve wording.
Diffstat (limited to 'etc/DEBUG')
-rw-r--r--etc/DEBUG10
1 files changed, 6 insertions, 4 deletions
diff --git a/etc/DEBUG b/etc/DEBUG
index c1b04eaf7f2..096bdbc48c9 100644
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -7,9 +7,9 @@ See the end of the file for license conditions.
[People who debug Emacs on Windows using Microsoft debuggers should
read the Windows-specific section near the end of this document.]
-** When you debug Emacs with GDB, you should start it in the directory
-where the executable was made (the 'src' directory in the Emacs source
-tree). That directory has a .gdbinit file that defines various
+** When you debug Emacs with GDB, you should start GDB in the directory
+where the Emacs executable was made (the 'src' directory in the Emacs
+source tree). That directory has a .gdbinit file that defines various
"user-defined" commands for debugging Emacs. (These commands are
described below under "Examining Lisp object values" and "Debugging
Emacs Redisplay problems".)
@@ -21,7 +21,9 @@ you will see a warning when GDB starts, like this:
warning: File ".../src/.gdbinit" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
There are several ways to overcome that difficulty, they are all
-described in the node "Auto-loading safe path" in the GDB user manual.
+described in the node "Auto-loading safe path" in the GDB user
+manual. If nothing else helps, type "source /path/to/.gdbinit RET" at
+the GDB prompt, to unconditionally load the GDB init file.
** When you are trying to analyze failed assertions or backtraces, it
is essential to compile Emacs with flags suitable for debugging.