comparison 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
comparison
equal deleted inserted replaced
35187:cb583146cc55 35188:94d46968a93f
737 737
738 @item 738 @item
739 If the symptom of the bug is that Emacs fails to respond, don't assume 739 If the symptom of the bug is that Emacs fails to respond, don't assume
740 Emacs is ``hung''---it may instead be in an infinite loop. To find out 740 Emacs is ``hung''---it may instead be in an infinite loop. To find out
741 which, make the problem happen under GDB and stop Emacs once it is not 741 which, make the problem happen under GDB and stop Emacs once it is not
742 responding. (If Emacs is using X Windows directly, you can stop Emacs 742 responding. (If Emacs is using X directly, you can stop Emacs by typing
743 by typing @kbd{C-z} at the GDB job.) Then try stepping with 743 @kbd{C-z} at the GDB job.) Then try stepping with @samp{step}. If
744 @samp{step}. If Emacs is hung, the @samp{step} command won't return. 744 Emacs is hung, the @samp{step} command won't return. If it is looping,
745 If it is looping, @samp{step} will return. 745 @samp{step} will return.
746 746
747 If this shows Emacs is hung in a system call, stop it again and examine 747 If this shows Emacs is hung in a system call, stop it again and examine
748 the arguments of the call. In your bug report, state exactly where in 748 the arguments of the call. In your bug report, state exactly where in
749 the source the system call is, and what the arguments are. 749 the source the system call is, and what the arguments are.
750 750