From a2ebb43f91f82bc25cbcd0a8b7136c9227ca159b Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Mon, 26 Mar 2007 03:28:55 +0000 Subject: [PATCH] Explain reason for X protocol error recommendations. --- etc/DEBUG | 13 +++++++++---- 1 file 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'. ** If you encounter X protocol errors -Try evaluating (x-synchronize t). That puts Emacs into synchronous -mode, where each Xlib call checks for errors before it returns. This -mode is much slower, but when you get an error, you will see exactly -which call really caused the error. +The X server normally reports protocol errors asynchronously, +so you find out about them long after the primitive which caused +the error has returned. + +To get clear information about the cause of an error, try evaluating +(x-synchronize t). That puts Emacs into synchronous mode, where each +Xlib call checks for errors before it returns. This mode is much +slower, but when you get an error, you will see exactly which call +really caused the error. You can start Emacs in a synchronous mode by invoking it with the -xrm option, like this: -- 2.11.4.GIT