unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: process_send_string blocks?
Date: Sat, 06 Sep 2014 03:09:22 -0500	[thread overview]
Message-ID: <85y4txdvbh.fsf@stephe-leake.org> (raw)

I'm trying to use a background process to parse buffer text, and send
results back to Emacs.

For large buffers, Emacs hangs; only killing the background process
externally recovers. This does not happen for small buffers (< 5k bytes?).

It appears that process-send-string is blocked on a full IO send queue,
while the background process is also blocked on a full IO send queue.

On reading process.c, I believe this should not happen, if the OS supports
EWOULDBLOCK. 

Is that true, even when there is only one call to process-send-string that
sends the entire buffer?

The doc string for process-send-string says "if > 500 chars, string is
sent in bunches", but I see no evidence of that in process.c. Is that
refering to the OS IO queue buffer size?

I'm running on Windows 7, using the Windows binary
emacs-23.4-bin-i386.zip from the FSF FTP site.

Is EWOULDBLOCK supported on this system?

I'll try compiling Emacs from source so I can run the debugger; I've
never tried that on Windows before.

I'd hate to have to code the partial read/partial write logic at the
elisp level.

-- 
-- Stephe



             reply	other threads:[~2014-09-06  8:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-06  8:09 Stephen Leake [this message]
2014-09-06  8:28 ` process_send_string blocks? Jorgen Schaefer
2014-09-06  9:34 ` Eli Zaretskii
2014-09-06 13:11   ` Stephen Leake
2014-09-06 13:28     ` Eli Zaretskii
2014-09-07  8:21       ` Stephen Leake
2014-09-07 15:44         ` Eli Zaretskii
2014-09-07 20:32           ` Stephen Leake

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=85y4txdvbh.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@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 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).