Commit 46def989 authored by Jan Djärv's avatar Jan Djärv
Browse files

Added note about xmon.

parent 0a1d6de0
2003-01-27 Jan Dj,Ad(Brv <>
* DEBUG: Added note about xmon.
2003-01-20 Joanna Pluta <>
* Updated.
......@@ -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
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.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment