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. |