/[emacs]/emacs/etc/DEBUG
ViewVC logotype

Diff of /emacs/etc/DEBUG

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.24 by eliz, Wed Apr 24 16:57:19 2002 UTC revision 1.25 by jhd, Mon Jan 27 19:59:07 2003 UTC
# Line 305  procedure: Line 305  procedure:
305    - You should now look around this offending X call and try to figure    - You should now look around this offending X call and try to figure
306      out what is wrong with it.      out what is wrong with it.
307    
308    ** If Emacs causes errors or memory leaks in your X server
309    
310    You can trace the traffic between Emacs and your X server with a tool
311    like xmon, available at ftp://ftp.x.org/contrib/devel_tools/.
312    
313    Xmon can be used to see exactly what Emacs sends when X protocol errors
314    happen.  If Emacs causes the X server memory usage to increase you can
315    use xmon to see what items Emacs creates in the server (windows,
316    graphical contexts, pixmaps) and what items Emacs delete.  If there
317    are consistently more creations than deletions, the type of item
318    and the activity you do when the items get created can give a hint where
319    to start debugging.
320    
321  ** If the symptom of the bug is that Emacs fails to respond  ** If the symptom of the bug is that Emacs fails to respond
322    
323  Don't assume Emacs is `hung'--it may instead be in an infinite loop.  Don't assume Emacs is `hung'--it may instead be in an infinite loop.

Legend:
Removed from v.1.24  
changed lines
  Added in v.1.25

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26