On 9/17/25 8:16 AM, Robert Elz wrote:
Date: Wed, 17 Sep 2025 20:04:58 +1000
From: Duncan Roe via Bug reports for the GNU Bourne Again SHell
<[email protected]>
Message-ID: <[email protected]>
| Do you by any chance have job control disabled?
I think a better question would be, which shell is being
used to run ./test0 & wait and ./test1 & wait.
And whether that shell is interactive. If you wrap the whole reproducer
up in a script, every shell behaves identically, as you say later.
It's all whether or not job control is enabled, which is what causes the
processes to be in different process groups.
That is what I suspect is happening, and why the difference between
test0 & test1 - it isn't a bug in the read command, that is acting
exactly as it should (ignoring the later core dump issue that Duncan
found, that is likely to be a bug for Chet to investigate - but it isn't,
directly anyway, related to the issue complained of here.)
This is correct.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU [email protected] http://tiswww.cwru.edu/~chet/
