[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/etc/DEBUG [lexbind]
From: |
Miles Bader |
Subject: |
[Emacs-diffs] Changes to emacs/etc/DEBUG [lexbind] |
Date: |
Mon, 25 Oct 2004 00:43:22 -0400 |
Index: emacs/etc/DEBUG
diff -c emacs/etc/DEBUG:1.24.2.2 emacs/etc/DEBUG:1.24.2.3
*** emacs/etc/DEBUG:1.24.2.2 Tue Oct 14 23:08:02 2003
--- emacs/etc/DEBUG Mon Oct 25 04:19:38 2004
***************
*** 69,77 ****
in the ordinary way, with the `p' command. Then type `pr' with no
arguments. This calls a subroutine which uses the Lisp printer.
! Note: It is not a good idea to try `pr' if you know that Emacs is in
! deep trouble: its stack smashed (e.g., if it encountered SIGSEGV due
! to stack overflow), or crucial data structures, such as `obarray',
corrupted, etc. In such cases, the Emacs subroutine called by `pr'
might make more damage, like overwrite some data that is important for
debugging the original problem.
--- 69,79 ----
in the ordinary way, with the `p' command. Then type `pr' with no
arguments. This calls a subroutine which uses the Lisp printer.
! You can also use `pp value' to print the emacs value directly.
!
! Note: It is not a good idea to try `pr' or `pp' if you know that Emacs
! is in deep trouble: its stack smashed (e.g., if it encountered SIGSEGV
! due to stack overflow), or crucial data structures, such as `obarray',
corrupted, etc. In such cases, the Emacs subroutine called by `pr'
might make more damage, like overwrite some data that is important for
debugging the original problem.
***************
*** 442,447 ****
--- 444,452 ----
Emacs compiled with GLYPH_DEBUG defined; type "C-h f dump- TAB" and
"C-h f trace- TAB" to see the full list.
+ When you debug display problems running emacs under X, you can use
+ the `ff' command to flush all pending display updates to the screen.
+
** Debugging LessTif
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] Changes to emacs/etc/DEBUG [lexbind],
Miles Bader <=