unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leon <sdl.web@gmail.com>
Subject: Re: gnus makes emacs lose response
Date: Fri, 07 Apr 2006 14:25:55 +0100	[thread overview]
Message-ID: <m2zmixzfdo.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: m3y7yherc3.fsf@kfs-l.imdomain.dk

storm@cua.dk (Kim F. Storm) writes:

> Leon <sdl.web@gmail.com> writes:
>
>> It seems when I compiled emacs I didn't turn on debug. I have followed
>> your instruction and get some debug info attached.
>>
>
> Thanks, but...
> .. without debugging information, the output from those commands
> is inadequate to diagnose the problem.
>

How can compile with debug information? I'll try to re-compile in a
week!

>> #0  0x0055b402 in __kernel_vsyscall ()
>> #1  0x0063a53d in ___newselect_nocancel () from /lib/libc.so.6
>> #2  0x0819b11e in wait_reading_process_output ()
>
> This is "near the spot" where I made the fix I mentioned.
> Maybe that fix isn't in your sources.  A simple way to check:
>
> If you do C-h C-f accept-process-output, do you get this result
> [check that the arguments are named SECONDS and MILLISEC] ??
>

Seems it's in my source.

,--------[ C-h f accept-process-output ]
| accept-process-output is a built-in function in `C source code'.
| (accept-process-output &optional PROCESS SECONDS MILLISEC
| JUST-THIS-ONE)
| 
| Allow any pending output from subprocesses to be read by Emacs.
| It is read into the process' buffers or given to their filter functions.
| Non-nil arg PROCESS means do not return until some output has been received
| from PROCESS.
| 
| Non-nil second arg SECONDS and third arg MILLISEC are number of
| seconds and milliseconds to wait; return after that much time whether
| or not there is input.  If SECONDS is a floating point number,
| it specifies a fractional number of seconds to wait.
| 
| If optional fourth arg JUST-THIS-ONE is non-nil, only accept output
| from PROCESS, suspending reading output from other processes.
| If JUST-THIS-ONE is an integer, don't run any timers either.
| Return non-nil iff we received any output before the timeout expired.
| 
| [back]
`--------

>
> accept-process-output is a built-in function in `C source code'.
> (accept-process-output &optional process seconds millisec
> just-this-one)
>
> Allow any pending output from subprocesses to be read by Emacs.
> It is read into the process' buffers or given to their filter functions.
> Non-nil arg process means do not return until some output has been received
> from process.
>
> Non-nil second arg seconds and third arg millisec are number of
> seconds and milliseconds to wait; return after that much time whether
> or not there is input.  If seconds is a floating point number,
> it specifies a fractional number of seconds to wait.
>
> If optional fourth arg just-this-one is non-nil, only accept output
> from process, suspending reading output from other processes.
> If just-this-one is an integer, don't run any timers either.
> Return non-nil iff we received any output before the timeout expired.

Thank you for explaining this.

-- 
Leon

  reply	other threads:[~2006-04-07 13:25 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2lkuuynpf.fsf@sl392.st-edmunds.cam.ac.uk>
     [not found] ` <m24q18rize.fsf@sl392.st-edmunds.cam.ac.uk>
2006-04-05  8:47   ` gnus makes emacs lose response Kim F. Storm
2006-04-05 17:55     ` Leon
2006-04-06  9:08       ` Kim F. Storm
2006-04-06 21:15         ` Leon
2006-04-07  8:13           ` Kim F. Storm
2006-04-07 13:25             ` Leon [this message]
2006-04-07 20:58         ` Ralf Angeli
2006-04-09  1:17           ` Leon
2006-04-17 20:35           ` Ralf Angeli
2006-04-18  1:46             ` Leon
2006-04-19 20:18               ` Ralf Angeli
2006-04-20  1:19                 ` Leon
2006-04-19 20:18             ` Ralf Angeli
2006-04-19 20:51               ` Stefan Monnier
2006-04-19 21:13                 ` Ralf Angeli
2006-04-20 18:05               ` Gregory Novak
2006-04-24  0:41                 ` Kim F. Storm
2006-08-22 11:44               ` Kim F. Storm
2006-08-23 14:45                 ` Richard Stallman
2006-08-23 15:00                   ` Kim F. Storm
2006-08-25  7:43                     ` Richard Stallman
2006-08-25  8:15                       ` Kim F. Storm
2006-08-26 10:08                         ` Richard Stallman
2006-08-26 21:32                           ` Kim F. Storm
2006-08-25  8:56                       ` Jason Rumney
2006-08-23 20:51                   ` Stefan Monnier
2006-08-24  3:17                   ` Bob Rogers
2006-08-24  7:51                     ` Kim F. Storm
2006-08-25  1:01                       ` Bob Rogers
2006-08-25 20:23                       ` Richard Stallman
2006-08-25  7:44                     ` Richard Stallman
2006-09-04  8:41 Kim F. Storm
2006-09-05 21:18 ` Chong Yidong
2006-09-05 21:21   ` Stefan Monnier
2006-09-07 20:43     ` Chong Yidong
2006-09-08 11:56       ` Richard Stallman
2006-09-06 19:06   ` Richard Stallman
2006-09-07 14:37 ` Chong Yidong
2006-09-22 20:04 ` Chong Yidong
2006-09-25  0:39   ` Stefan Monnier
2006-09-25 15:22     ` Chong Yidong
  -- strict thread matches above, loose matches on Subject: below --
2006-09-09 22:33 Kim F. Storm
2006-09-10  4:10 ` Stefan Monnier
2006-09-16 20:22   ` Chong Yidong
2006-09-18 14:40   ` Chong Yidong
2006-09-18 14:53     ` Chong Yidong
2006-09-19 10:45       ` Stefan Monnier
2006-09-19 15:02         ` Chong Yidong
2006-09-22 19:12           ` Stefan Monnier
2006-09-23 18:01             ` Richard Stallman
2006-09-23  3:34         ` Richard Stallman
2006-09-23 15:02           ` Stefan Monnier
2006-09-18 14:55     ` Stefan Monnier
2006-09-23 18:18 Chong Yidong
2006-09-23 23:42 ` Luc Teirlinck
2006-09-26 17:26 ` Leo
2006-09-26 18:08   ` Chong Yidong
2006-09-26 19:20     ` Leo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2zmixzfdo.fsf@sl392.st-edmunds.cam.ac.uk \
    --to=sdl.web@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).