Mercurial > emacs
comparison etc/DEBUG @ 76739:e4f81c51941e
Explain reason for X protocol error recommendations.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Mon, 26 Mar 2007 03:28:55 +0000 |
parents | dc23aaa67696 |
children | 563a04f93ea0 4ef881a120fe |
comparison
equal
deleted
inserted
replaced
76738:c39f6a4ef598 | 76739:e4f81c51941e |
---|---|
304 problem happens in an undumped Emacs. To run `temacs' under a | 304 problem happens in an undumped Emacs. To run `temacs' under a |
305 debugger, type "gdb temacs", then start it with `r -batch -l loadup'. | 305 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 |
309 Try evaluating (x-synchronize t). That puts Emacs into synchronous | 309 The X server normally reports protocol errors asynchronously, |
310 mode, where each Xlib call checks for errors before it returns. This | 310 so you find out about them long after the primitive which caused |
311 mode is much slower, but when you get an error, you will see exactly | 311 the error has returned. |
312 which call really caused the error. | 312 |
313 To get clear information about the cause of an error, try evaluating | |
314 (x-synchronize t). That puts Emacs into synchronous mode, where each | |
315 Xlib call checks for errors before it returns. This mode is much | |
316 slower, but when you get an error, you will see exactly which call | |
317 really caused the error. | |
313 | 318 |
314 You can start Emacs in a synchronous mode by invoking it with the -xrm | 319 You can start Emacs in a synchronous mode by invoking it with the -xrm |
315 option, like this: | 320 option, like this: |
316 | 321 |
317 emacs -xrm "emacs.synchronous: true" | 322 emacs -xrm "emacs.synchronous: true" |