From 46def98960543fce36b1c3cb16fe5b0444d30052 Mon Sep 17 00:00:00 2001 From: Jan Djärv Date: Mon, 27 Jan 2003 19:59:08 +0000 Subject: Added note about xmon. --- etc/ChangeLog | 4 ++++ etc/DEBUG | 13 +++++++++++++ 2 files changed, 17 insertions(+) diff --git a/etc/ChangeLog b/etc/ChangeLog index 27bd4eede3..f3f109098d 100644 --- a/etc/ChangeLog +++ b/etc/ChangeLog @@ -1,3 +1,7 @@ +2003-01-27 Jan Dj,Ad(Brv + + * DEBUG: Added note about xmon. + 2003-01-20 Joanna Pluta * TUTORIAL.pl: Updated. diff --git a/etc/DEBUG b/etc/DEBUG index dd2b58d3f7..a0ac04d4ab 100644 --- a/etc/DEBUG +++ b/etc/DEBUG @@ -305,6 +305,19 @@ procedure: - You should now look around this offending X call and try to figure out what is wrong with it. +** If Emacs causes errors or memory leaks in your X server + +You can trace the traffic between Emacs and your X server with a tool +like xmon, available at ftp://ftp.x.org/contrib/devel_tools/. + +Xmon can be used to see exactly what Emacs sends when X protocol errors +happen. If Emacs causes the X server memory usage to increase you can +use xmon to see what items Emacs creates in the server (windows, +graphical contexts, pixmaps) and what items Emacs delete. If there +are consistently more creations than deletions, the type of item +and the activity you do when the items get created can give a hint where +to start debugging. + ** If the symptom of the bug is that Emacs fails to respond Don't assume Emacs is `hung'--it may instead be in an infinite loop. -- cgit v1.2.3