diff options
author | Eli Zaretskii <eliz@gnu.org> | 2001-01-10 08:15:32 +0000 |
---|---|---|
committer | Eli Zaretskii <eliz@gnu.org> | 2001-01-10 08:15:32 +0000 |
commit | 97878c08e08151528135ae911f69ad627360ff3b (patch) | |
tree | 9bada862e123a103c65dbcc8d9c15e1a1a42edb5 /man/trouble.texi | |
parent | 402324527e3f282cfc70f0c5d5577b7be80b26db (diff) | |
download | emacs-97878c08e08151528135ae911f69ad627360ff3b.tar.gz |
Don't say "X Windows". From Colin Walters <walters@cis.ohio-state.edu>.
Diffstat (limited to 'man/trouble.texi')
-rw-r--r-- | man/trouble.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/man/trouble.texi b/man/trouble.texi index 3f68690f8eb..fde07235728 100644 --- a/man/trouble.texi +++ b/man/trouble.texi @@ -739,10 +739,10 @@ had a fatal signal. 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 |