From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: fatal flaw zsh 4.0.1 on irix 6.3 & 6.5: suspend "ls -l|less" then resume hangs
Date: Wed, 11 Jul 2001 10:33:17 +0200 (MET DST) [thread overview]
Message-ID: <200107110833.KAA17304@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <010710162700.ZM30017@candle.brasslantern.com>
Bart Schaefer wrote:
> On Jul 10, 5:26pm, Timothy Miller wrote:
> >
> > Ok: zsh-3_1_6-pws-2 works; zsh-3_1_6-pws-3 fails.
>
> One of these must be the culprit, then:
>
> * Sven: 7605: Src/exec.c, Src/jobs.c: use killpg instead of
> altering process group when leader exits, fix fg test to use
> killpg.
>
> * Sven: 7573: Src/signals.c, Src/exec.c, Src/utils.c: fix return
> value of killjb(); pipelines which lose their leader get a new
> one.
>
> Can you send us some output of `ps' that shows the process groups of the
> processes involved, from both -pws-2 and anything after that?
You may also try the patch below (each hunk separately or both together).
If this turns out to be the problem, then Irix seems to behave
differently from other Unices w.r.t. calling kill() on a process group
with `signal' 0. Urgh.
Bye
Sven
--- Src/exec.c.old Wed Jul 11 10:27:51 2001
+++ Src/exec.c Wed Jul 11 10:28:19 2001
@@ -2512,7 +2512,7 @@
} else if (thisjob != -1 && cl) {
if (jobtab[list_pipe_job].gleader && (list_pipe || list_pipe_child)) {
if (setpgrp(0L, jobtab[list_pipe_job].gleader) == -1 ||
- killpg(jobtab[list_pipe_job].gleader, 0) == -1) {
+ kill(jobtab[list_pipe_job].gleader, 0) == -1) {
jobtab[list_pipe_job].gleader =
jobtab[thisjob].gleader = (list_pipe_child ? mypgrp : getpid());
setpgrp(0L, jobtab[list_pipe_job].gleader);
--- Src/utils.c.old Wed Jul 11 10:33:09 2001
+++ Src/utils.c Wed Jul 11 10:33:16 2001
@@ -2404,7 +2404,7 @@
# endif
#endif
{
- if (pgrp != mypgrp && kill(-pgrp, 0) == -1)
+ if (pgrp != mypgrp && kill(pgrp, 0) == -1)
attachtty(mypgrp);
else {
if (errno != ENOTTY)
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev parent reply other threads:[~2001-07-11 8:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 15:11 Timothy Miller
2001-06-12 8:15 ` Sven Wischnowsky
2001-06-12 15:00 ` Timothy Miller
[not found] ` <1010612154026.ZM24394@candle.brasslantern.com>
2001-06-12 16:13 ` Timothy Miller
2001-06-13 3:55 ` Bart Schaefer
2001-07-06 22:40 ` Timothy Miller
2001-06-14 7:32 ` Sven Wischnowsky
2001-07-06 22:52 ` Timothy Miller
2001-07-10 15:22 ` Timothy Miller
2001-07-10 16:25 ` Bart Schaefer
2001-07-10 21:26 ` Timothy Miller
2001-07-10 23:27 ` Bart Schaefer
2001-07-11 8:33 ` Sven Wischnowsky [this message]
2001-07-11 9:51 ` Sven Wischnowsky
2001-07-11 18:59 ` Timothy Miller
2001-07-12 3:39 ` Bart Schaefer
2001-07-30 20:18 ` Timothy Miller
2001-07-30 21:24 ` Bart Schaefer
2001-07-30 22:08 ` Timothy Miller
2001-07-31 8:20 ` Sven Wischnowsky
2001-07-31 8:30 ` Borsenkow Andrej
2001-07-31 14:35 ` Timothy Miller
2001-07-31 20:50 ` Timothy Miller
2001-08-01 8:35 ` Sven Wischnowsky
2002-02-25 9:31 ` Sven Wischnowsky
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=200107110833.KAA17304@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.dk \
/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).