Mercurial > emacs
changeset 43432:7fe131ded6d9
*** empty log message ***
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Wed, 20 Feb 2002 22:24:59 +0000 |
| parents | 438494390a90 |
| children | bacf1b0c4081 |
| files | etc/DEBUG |
| diffstat | 1 files changed, 6 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- 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.