From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Bug related to stdin/always/jobcontrol
Date: Thu, 15 Sep 2016 18:08:55 -0700 [thread overview]
Message-ID: <160915180855.ZM3928@torch.brasslantern.com> (raw)
In-Reply-To: <20160915184040.5fc1b9d0@pwslap01u.europe.root.pri>
On Sep 15, 6:40pm, Peter Stephenson wrote:
} Subject: Re: Bug related to stdin/always/jobcontrol
}
} The race is related to the fact that when the new SUPERJOB takes over
} it's actually in the same process group as the SUBJOB it's taking over,
} which is different from it's own PID, list_pipe_pid [...]
}
} However, fixing that up doesn't help --- apparently attaching it to the
} TTY after the SUBJOB is finished works OK, sending it SIGCONT seems to
} be OK, but then it always gets SIGSTOP
Is it definitely getting SIGSTOP and not SIGTSTP ?
The operating system will never[*] automatically send a true STOP signal
because it's un-catchable. If a STOP is being received, it's probably
being sent from the "for (; !nowait;)" loop in execpline(), either at
line 1674 [ killpg(jobtab[list_pipe_job].gleader, SIGSTOP); ] or at
line 1688 [ kill(getpid(), SIGSTOP); ].
[*] To my knowledge, anyway.
} I think the code is enough better that I may submit it and wonder what
} to do with the remaining problem later, or let Bart have a go when he
} gets some time.
That seems reasonable. This isn't any worse than it ever was, so it
shouldn't hold up the release.
next prev parent reply other threads:[~2016-09-16 1:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 18:39 Christian Neukirchen
2016-09-05 15:04 ` Christian Neukirchen
2016-09-05 15:42 ` Peter Stephenson
[not found] ` <CGME20160914173110eucas1p1f0567e319ae439b975b19f4e55676fed@eucas1p1.samsung.com>
2016-09-14 17:31 ` Peter Stephenson
2016-09-14 21:35 ` Peter Stephenson
2016-09-15 3:24 ` Bart Schaefer
2016-09-15 8:27 ` Peter Stephenson
2016-09-15 10:33 ` Peter Stephenson
2016-09-15 17:40 ` Peter Stephenson
2016-09-16 1:08 ` Bart Schaefer [this message]
2016-09-16 12:02 ` Peter Stephenson
2016-09-22 11:59 ` Daniel Shahaf
2016-09-22 16:38 ` Bart Schaefer
2016-09-23 1:18 ` Bart Schaefer
2016-09-23 6:06 ` Daniel Shahaf
2016-09-25 14:39 ` Peter Stephenson
2016-09-25 22:54 ` struct job.other (was Re: Bug related to stdin/always/jobcontrol) Bart Schaefer
2016-09-26 11:20 ` Peter Stephenson
2016-09-26 16:33 ` Bart Schaefer
2016-09-25 15:16 ` Bug related to stdin/always/jobcontrol Peter Stephenson
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=160915180855.ZM3928@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).