[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug in force_interactive handling

From: Stas Sergeev
Subject: Re: bug in force_interactive handling
Date: Fri, 30 Dec 2011 14:36:13 +0400
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16

Hello Chet, thanks for your patch file.
It is slightly broken, attached is the fixed version
of your patch.
BUT: it solves only half of the bug.
Please check it yourself, here's the script:
#!./bash -i
set -m; cat
echo Finished!
while :; do jobs; sleep 2; done

Run this script, then do
killall -STOP cat
You'll start seeing the output of "jobs" every 2 seconds,
and the cat is marked "Stopped".
Then do
killall -CONT cat
Nothing changes, the cat is still listed as stopped.
Then bash will run terminate_stopped_jobs() on it. :(
Do you know how to fix also this?

29.12.2011 20:54, Chet Ramey wrote:
> When you run bash with -i, interactive and interactive_shell are set
> when initialize_job_control is called, so the correct initialization
> happens.  It's only later that job control gets turned off inappropriately.
As a side note it would be nice to not flip the "interactive"
value back and forth to make the code understanding

Attachment: interact.diff
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]