[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/etc/DEBUG,v
From: |
Eli Zaretskii |
Subject: |
[Emacs-diffs] Changes to emacs/etc/DEBUG,v |
Date: |
Fri, 23 Jun 2006 18:14:57 +0000 |
CVSROOT: /cvsroot/emacs
Module name: emacs
Changes by: Eli Zaretskii <eliz> 06/06/23 18:14:57
Index: DEBUG
===================================================================
RCS file: /cvsroot/emacs/emacs/etc/DEBUG,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -b -r1.40 -r1.41
--- DEBUG 23 Jun 2006 14:37:10 -0000 1.40
+++ DEBUG 23 Jun 2006 18:14:57 -0000 1.41
@@ -20,6 +20,8 @@
** When you debug Emacs with GDB, you should start it in the directory
where the executable was made. That directory has a .gdbinit file
that defines various "user-defined" commands for debugging Emacs.
+(These commands are described below under "Examining Lisp object
+values" and "Debugging Emacs Redisplay problems".)
** When you are trying to analyze failed assertions, it will be
essential to compile Emacs either completely without optimizations or
@@ -276,9 +278,9 @@
the GDB Graphical Interface node of the Emacs manual). There are also some
features available just for debugging Emacs:
-1) The command gud-pp isavailable on the tool bar (the `pp' icon) and allows
- the user to print the s-expression of the variable at point, in the GUD
- buffer.
+1) The command gud-pp is available on the tool bar (the `pp' icon) and
+ allows the user to print the s-expression of the variable at point,
+ in the GUD buffer.
2) Pressing `p' on a component of a watch expression that is a lisp object
in the speedbar prints its s-expression in the GUD buffer.