From 1ce9f40ad4ecdb669c8c57a6cf3994e7fa9b0474 Mon Sep 17 00:00:00 2001 From: "Kim F. Storm" Date: Mon, 4 Oct 2004 13:37:01 +0000 Subject: Mention pp and ff commands. --- etc/DEBUG | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) (limited to 'etc/DEBUG') diff --git a/etc/DEBUG b/etc/DEBUG index bcc0bd8418..6419b3dfd8 100644 --- a/etc/DEBUG +++ b/etc/DEBUG @@ -69,9 +69,11 @@ fatal error, you can use the GDB command `pr'. First print the value 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', +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,6 +444,9 @@ Several more functions for debugging display code are available in 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 -- cgit v1.2.3