Mercurial > emacs
changeset 49489:e0ff22ddc744
Added note about xmon.
| author | Jan Djärv <jan.h.d@swipnet.se> |
|---|---|
| date | Mon, 27 Jan 2003 19:59:08 +0000 |
| parents | da6abcaef15c |
| children | 567f8c656a28 |
| files | etc/ChangeLog etc/DEBUG |
| diffstat | 2 files changed, 17 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/etc/ChangeLog Mon Jan 27 19:36:10 2003 +0000 +++ b/etc/ChangeLog Mon Jan 27 19:59:08 2003 +0000 @@ -1,3 +1,7 @@ +2003-01-27 Jan Dj,Ad(Brv <jan.h.d@swipnet.se> + + * DEBUG: Added note about xmon. + 2003-01-20 Joanna Pluta <joanna_p@gazeta.pl> * TUTORIAL.pl: Updated.
--- a/etc/DEBUG Mon Jan 27 19:36:10 2003 +0000 +++ b/etc/DEBUG Mon Jan 27 19:59:08 2003 +0000 @@ -305,6 +305,19 @@ - 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.