Mercurial > emacs
diff man/trouble.texi @ 35188:94d46968a93f
Don't say "X Windows". From Colin Walters <walters@cis.ohio-state.edu>.
author | Eli Zaretskii <eliz@gnu.org> |
---|---|
date | Wed, 10 Jan 2001 08:15:32 +0000 |
parents | 2d29e09cdef7 |
children | a4e73c75cbca |
line wrap: on
line diff
--- a/man/trouble.texi Tue Jan 09 23:49:44 2001 +0000 +++ b/man/trouble.texi Wed Jan 10 08:15:32 2001 +0000 @@ -739,10 +739,10 @@ 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. To find out which, make the problem happen under GDB and stop Emacs once it is not -responding. (If Emacs is using X Windows directly, you can stop Emacs -by typing @kbd{C-z} at the GDB job.) Then try stepping with -@samp{step}. If Emacs is hung, the @samp{step} command won't return. -If it is looping, @samp{step} will return. +responding. (If Emacs is using X directly, you can stop Emacs by typing +@kbd{C-z} at the GDB job.) Then try stepping with @samp{step}. If +Emacs is hung, the @samp{step} command won't return. If it is looping, +@samp{step} will return. If this shows Emacs is hung in a system call, stop it again and examine the arguments of the call. In your bug report, state exactly where in