summaryrefslogtreecommitdiff
path: root/etc/DEBUG
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2001-03-23 12:38:16 +0000
committerEli Zaretskii <eliz@gnu.org>2001-03-23 12:38:16 +0000
commitec4054f004dca3f84c30e60646ec5bd71dae9c56 (patch)
tree2513d184f1e9f91513c56ff0c5f973e29fdcbcbd /etc/DEBUG
parent091f887891422b7fc5e769b62c76cc6600ccc7b1 (diff)
downloademacs-ec4054f004dca3f84c30e60646ec5bd71dae9c56.tar.gz
Document the use of -xrm to start EMacs in synchronous mode.
Diffstat (limited to 'etc/DEBUG')
-rw-r--r--etc/DEBUG9
1 files changed, 9 insertions, 0 deletions
diff --git a/etc/DEBUG b/etc/DEBUG
index 032aeb4dcd5..c26f090cc3a 100644
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -249,6 +249,15 @@ 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:
+
+ emacs -rm "emacs.synchronous: true"
+
+Setting a breakpoint in the function `x_error_quitter' and looking at
+the backtrace when Emacs stops inside that function will show what
+code causes the X protocol errors.
+
** 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.