zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: coprocess descriptor and error messages
Date: Fri, 17 Sep 2010 09:11:43 -0700	[thread overview]
Message-ID: <100917091143.ZM31859@torch.brasslantern.com> (raw)
In-Reply-To: <100917074136.ZM31402@torch.brasslantern.com>

On Sep 17,  7:41am, Bart Schaefer wrote:
}
} Aside:  Should an interactive shell ever exit on SIGPIPE?  Or maybe
} a better question is, should a print to the coprocess ever cause an
} un-trapped SIGPIPE?

Experimenting with pdksh seems to indicate that the equivalent of
zsh's coprocout descriptor is closed in the child-exited handler
when the coprocess terminates.  I don't recall enough about (and
didn't yet delve back into) the zsh job table to know if we have
enough information to identify the coprocess job at that point.

The coprocin descriptor remains open until EOF, as in zsh.

} In looking further, the coprocess descriptor is reset to -1 only (and
} immediately) by "read -p" detecting EOF on the coprocess output.  So
} in the "read" case, the invalid descriptor has always served as an
} EOF flag.  What should happen if the parent attempts to read after
} an EOF has been seen?  I would tend to think it should just get EOF
} again, not produce a diagnostic, which is the current behavior. 
} 
} However, ksh (at least pdksh) disagrees with me:

Here's a patch that duplicates the pdksh behavior, except for the part
about exiting on SIGPIPE if an extra print occurs before all output
has been read.  Apply this *instead* of the previous patch.

Index: builtin.c
===================================================================
RCS file: /extra/cvsroot/zsh/zsh-4.0/Src/builtin.c,v
retrieving revision 1.48
diff -c -r1.48 builtin.c
--- builtin.c	17 Apr 2009 18:57:22 -0000	1.48
+++ builtin.c	17 Sep 2010 15:59:06 -0000
@@ -3677,13 +3720,21 @@
     if (OPT_HASARG(ops,'u') || OPT_ISSET(ops,'p')) {
 	int fd;
 
-	if (OPT_ISSET(ops, 'p'))
+	if (OPT_ISSET(ops, 'p')) {
 	    fd = coprocout;
-	else {
+	    if (fd < 0) {
+		zwarnnam(name, "-p: no coprocess");
+		return 1;
+	    }
+	} else {
 	    char *argptr = OPT_ARG(ops,'u'), *eptr;
 	    /* Handle undocumented feature that -up worked */
 	    if (!strcmp(argptr, "p")) {
 		fd = coprocout;
+		if (fd < 0) {
+		    zwarnnam(name, "-p: no coprocess");
+		    return 1;
+		}
 	    } else {
 		fd = (int)zstrtol(argptr, &eptr, 10);
 		if (*eptr) {
@@ -5038,6 +5099,10 @@
 	/* The old code handled -up, but that was never documented. Still...*/
 	if (!strcmp(argptr, "p")) {
 	    readfd = coprocin;
+	    if (readfd < 0) {
+		zwarnnam(name, "-p: no coprocess");
+		return 1;
+	    }
 	} else {
 	    readfd = (int)zstrtol(argptr, &eptr, 10);
 	    if (*eptr) {
@@ -5052,6 +5117,10 @@
 	izle = 0;
     } else if (OPT_ISSET(ops,'p')) {
 	readfd = coprocin;
+	if (readfd < 0) {
+	    zwarnnam(name, "-p: no coprocess");
+	    return 1;
+	}
 	izle = 0;
     } else
 	readfd = izle = 0;


      reply	other threads:[~2010-09-17 16:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-17  5:04 Bart Schaefer
2010-09-17  8:46 ` Peter Stephenson
2010-09-17 14:41   ` Bart Schaefer
2010-09-17 16:11     ` Bart Schaefer [this message]

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=100917091143.ZM31859@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).