Article View: gnu.emacs.bug
Article #98554Re: hang the debugger (in GNUS)
From: Dan_Jacobson
Date: Fri, 24 May 1991 22:44
Date: Fri, 24 May 1991 22:44
65 lines
3108 bytes
3108 bytes
[this report "closes out" my previous report. Conclusion: "I'm dumb,
no bug, never mind"]
[original misguided complaint:]
>>>>> On 10 May 91 16:15:00 GMT, Dan_Jacobson@ATT.COM said:
Dumb_Dan> [sent to both gnu.emacs.bug & gnu.emacs.gnus]
Dumb_Dan> [GNUS 3.13, emacs 18.55,57 SYS V & Sun]
Dumb_Dan> Do:
Dumb_Dan> start up gnus
Dumb_Dan> do (debug-on-entry (quote nntp-accept-response))
Dumb_Dan> select a newsgroup (space bar)
Dumb_Dan> you step ("d") along until the screen says
Dumb_Dan> Entering:
Dumb_Dan> * accept-process-output(#<process nntpd>)
Dumb_Dan> [...]
Dumb_Dan> * nntp-accept-response()
Dumb_Dan> then you hang (if you are using the debugger)...
[solution:]
>>>>> On Thu, 23 May 91 00:29:20 +0200, linus@LYSATOR.LiU.SE (Linus Tolke) said:
Linus> From emacs documentation:
Linus> Accepting Output from Processes
Linus> -------------------------------
Linus> Output from asynchronous subprocesses normally arrives only while
Linus> Emacs is waiting for some sort of external event, such as elapsed
Linus> time or terminal input. Occasionally it is useful in a Lisp program
Linus> to explicitly permit output to arrive at a specific point, or even to
Linus> wait until output arrives from a process.
Linus> * Function: accept-process-output &optional PROCESS
Linus> This function allows Emacs to read pending output from
Linus> processes. The output is inserted in the associated buffers or
Linus> given to their filter functions. If PROCESS is non-`nil' then
Linus> this function does not return until some output has been
Linus> received from PROCESS.
Linus> End emacs documentation.
Linus> Obvious?
Linus> When you are running gnus under the debugger you sometimes let the
Linus> emacs wait (for you to type d). Then the output from the process is
Linus> read and when you (finally) arrive to the accept-process-output there
Linus> is nothing more to be read so you hang.
Linus> If you really want to run gnus under the debugger you will have to set
Linus> the nntp-buggy-select flag.
Linus> (setq nntp-buggy-select t)
Linus> Read the documentation for nntp-buggy-select.
Linus> --
Linus> /Linus
Linus> ***** Wherever I exec my `which emacs`, is my $HOME. *****
Linus> Linus Tolke SM7OUU, linus@lysator.liu.se
Linus> Student at the member of SK5EU LiTHSA
Linus> Link|ping institute of technology, LiTH LiTH S{ndare Amat|rer (Ham-club)
Technical Details
Message-ID:
<1991May24.224447.2699@cbfsb.att.com>Path:
arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!cis.ohio-state.edu!tut.cis.ohio-state.edu!unreplyable!garbageShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fb2f1,a57bbc8ce7311e16,start X-Google-Attributes: gidfb2f1,public X-Google-ArrivalTime: 1991-05-24 15:44:47 PST Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!cis.ohio-state.edu!tut.cis.ohio-state.edu!unreplyable!garbage From: Dan_Jacobson@ATT.COM Newsgroups: gnu.emacs.bug Subject: Re: hang the debugger (in GNUS) Message-ID: <1991May24.224447.2699@cbfsb.att.com> Date: 24 May 91 22:44:47 GMT Sender: daemon@tut.cis.ohio-state.edu Reply-To: Dan_Jacobson@ihlpz.att.com Distribution: gnu Organization: AT&T-BL, Naperville IL, USA Lines: 65 Approved: bug-gnu-emacs@prep.ai.mit.edu