From: Richard Stallman <rms@gnu.org>
Subject: Unreliability in process output
Date: Tue, 07 Jun 2005 08:25:02 -0400 [thread overview]
Message-ID: <E1Dfd8g-0006k3-Bl@fencepost.gnu.org> (raw)
After emacs -Q, visiting src/window.c and then doing C-x v l gives
unreliable results. Large chunks of the buffer are missing. Which
parts are missing varies each time, but the first missing chunk seems
to start on a 4096-character boundary.
The problem still happens if process-adaptive-read-buffering is nil
and coding-system-for-read is no-conversion. I've determined that the
variable carryover in read_process_output is always zero in that mode.
When I tried this with a breakpoint at read_process_output, and paused
for some time in that breakpoint, the text obtained consisted of the
first chunk plus a little more; nearly all was lost.
Stepping through read_process_output showed that the only calls
to emacs_read were from read_process_output, and that the text they
read was the text that appeared in the buffer. Somehow the rest
of the text is disappearing.
Similar problems happen with an executable I compiled almost 3 years
ago. It is not a newly introduced problem.
Can anyone else observe this problem? Can anyone make more headway
debugging this?
next reply other threads:[~2005-06-07 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 12:25 Richard Stallman [this message]
2005-06-07 12:51 ` Unreliability in process output Nick Roberts
2005-06-07 12:57 ` Kim F. Storm
2005-06-08 12:02 ` Richard Stallman
2005-06-08 12:45 ` Andreas Schwab
2005-06-08 14:23 ` Robert J. Chassell
2005-06-07 13:14 ` Andreas Schwab
2005-06-08 10:18 ` public
2005-06-08 11:34 ` Andreas Schwab
2005-06-08 12:02 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Dfd8g-0006k3-Bl@fencepost.gnu.org \
--to=rms@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.