[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/etc/DEBUG
From: |
Jan Djärv |
Subject: |
[Emacs-diffs] Changes to emacs/etc/DEBUG |
Date: |
Mon, 27 Jan 2003 14:59:08 -0500 |
Index: emacs/etc/DEBUG
diff -c emacs/etc/DEBUG:1.24 emacs/etc/DEBUG:1.25
*** emacs/etc/DEBUG:1.24 Wed Apr 24 12:57:19 2002
--- emacs/etc/DEBUG Mon Jan 27 14:59:07 2003
***************
*** 305,310 ****
--- 305,323 ----
- 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.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] Changes to emacs/etc/DEBUG,
Jan Djärv <=