From 42a3c62765b43eee3586e5ba023a2e6d25c724d2 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Wed, 20 Feb 2002 22:24:59 +0000 Subject: [PATCH] *** empty log message *** --- etc/DEBUG | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/etc/DEBUG b/etc/DEBUG index 7ae4ab9c46d..983437bc20e 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. -- 2.39.5