# HG changeset patch # User Richard M. Stallman # Date 1014243899 0 # Node ID 7fe131ded6d91e0cc0cf4b7cdda707a155b0b33b # Parent 438494390a907bd5c9611b470fea2474d4458ed5 *** empty log message *** diff -r 438494390a90 -r 7fe131ded6d9 etc/DEBUG --- a/etc/DEBUG Wed Feb 20 17:42:40 2002 +0000 +++ b/etc/DEBUG Wed Feb 20 22:24:59 2002 +0000 @@ -16,13 +16,17 @@ 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.