aboutsummaryrefslogtreecommitdiffstats
path: root/etc
diff options
context:
space:
mode:
authorRichard M. Stallman <[email protected]>2002-02-20 22:24:59 +0000
committerRichard M. Stallman <[email protected]>2002-02-20 22:24:59 +0000
commit42a3c62765b43eee3586e5ba023a2e6d25c724d2 (patch)
tree02db46feff98114ad31fa41281b8c0440599ea97 /etc
parent31b62ac19e008fe9a2e7780c3228bf81e3b62daf (diff)
*** empty log message ***
Diffstat (limited to 'etc')
-rw-r--r--etc/DEBUG8
1 files changed, 6 insertions, 2 deletions
diff --git a/etc/DEBUG b/etc/DEBUG
index 7ae4ab9c46..983437bc20 100644
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -16,13 +16,17 @@ Copyright (c) 1985, 2000, 2001 Free Software Foundation, Inc.
should read the Windows-specific section near the end of this
document.]
-It is a good idea to run Emacs under GDB (or some other suitable
+** When you debug Emacs with GDB, you should start it in the directory
+where you built Emacs. That directory has a .gdbinit file that defines
+various "user-defined" commands for debugging Emacs.
+
+** It is a good idea to run Emacs under GDB (or some other suitable
debugger) *all the time*. Then, when Emacs crashes, you will be able
to debug the live process, not just a core dump. (This is especially
important on systems which don't support core files, and instead print
just the registers and some stack addresses.)
-If Emacs hangs, or seems to be stuck in some infinite loop, typing
+** If Emacs hangs, or seems to be stuck in some infinite loop, typing
"kill -TSTP PID", where PID is the Emacs process ID, will cause GDB to
kick in, provided that you run under GDB.