Added note about xmon.

diff --git a/etc/ChangeLog b/etc/ChangeLog
index 27bd4eede3fd103859b407a55f9a1d4a0a2734ba..f3f109098df3ca4b4262669aefad610ed651d7a2 100644 (file)
--- a/etc/ChangeLog
+++ b/etc/ChangeLog
@@ -1,3 +1,7 @@
+2003-01-27  Jan Dj\e,Ad\e(Brv  <jan.h.d@swipnet.se>
+
+       * DEBUG: Added note about xmon.
+
 2003-01-20  Joanna Pluta  <joanna_p@gazeta.pl>
 
        * TUTORIAL.pl: Updated.

diff --git a/etc/DEBUG b/etc/DEBUG
index dd2b58d3f7ff486375392d4db419431f4bbdc235..a0ac04d4ab018488cfc0fe967c22394adce4f73b 100644 (file)
--- 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.