emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] Changes to emacs/etc/DEBUG


From: Richard M. Stallman
Subject: [Emacs-diffs] Changes to emacs/etc/DEBUG
Date: Wed, 20 Feb 2002 17:24:59 -0500

Index: emacs/etc/DEBUG
diff -c emacs/etc/DEBUG:1.22 emacs/etc/DEBUG:1.23
*** emacs/etc/DEBUG:1.22        Mon Feb  4 07:50:26 2002
--- emacs/etc/DEBUG     Wed Feb 20 17:24:59 2002
***************
*** 16,28 ****
  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
  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
  "kill -TSTP PID", where PID is the Emacs process ID, will cause GDB to
  kick in, provided that you run under GDB.
  
--- 16,32 ----
  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 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
  "kill -TSTP PID", where PID is the Emacs process ID, will cause GDB to
  kick in, provided that you run under GDB.
  



reply via email to

[Prev in Thread] Current Thread [Next in Thread]