aboutsummaryrefslogtreecommitdiffstats
path: root/etc/DEBUG
diff options
context:
space:
mode:
authorRichard M. Stallman2007-03-26 03:28:55 +0000
committerRichard M. Stallman2007-03-26 03:28:55 +0000
commita2ebb43f91f82bc25cbcd0a8b7136c9227ca159b (patch)
tree33051561fec5a9aa0aed02d2553d4b7b10d58666 /etc/DEBUG
parent8f0e1e444f4102b9593dae0a6035f53f61f49c2f (diff)
downloademacs-a2ebb43f91f82bc25cbcd0a8b7136c9227ca159b.tar.gz
emacs-a2ebb43f91f82bc25cbcd0a8b7136c9227ca159b.zip
Explain reason for X protocol error recommendations.
Diffstat (limited to 'etc/DEBUG')
-rw-r--r--etc/DEBUG13
1 files changed, 9 insertions, 4 deletions
diff --git a/etc/DEBUG b/etc/DEBUG
index ad59d48b3ca..97e1f015a05 100644
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -306,10 +306,15 @@ debugger, type "gdb temacs", then start it with `r -batch -l loadup'.
306 306
307** If you encounter X protocol errors 307** If you encounter X protocol errors
308 308
309Try evaluating (x-synchronize t). That puts Emacs into synchronous 309The X server normally reports protocol errors asynchronously,
310mode, where each Xlib call checks for errors before it returns. This 310so you find out about them long after the primitive which caused
311mode is much slower, but when you get an error, you will see exactly 311the error has returned.
312which call really caused the error. 312
313To get clear information about the cause of an error, try evaluating
314(x-synchronize t). That puts Emacs into synchronous mode, where each
315Xlib call checks for errors before it returns. This mode is much
316slower, but when you get an error, you will see exactly which call
317really caused the error.
313 318
314You can start Emacs in a synchronous mode by invoking it with the -xrm 319You can start Emacs in a synchronous mode by invoking it with the -xrm
315option, like this: 320option, like this: