Re: Bug: Subshell won't continue after .-sourcing a file

[Dan Church]

Awesome Chet!

Confirmed fixed by your patch. Do you think you'll include my test for 
the bug?

Here is an updated script that uses proper quoting everywhere:

        sub1=$(mktemp)
        sub2=$(mktemp)
        sub3=$(mktemp)

        echo "( echo '1st script executing' ; . ${sub2@Q} ; echo '1st script still executing' 
)" >"$sub1"
        echo "echo '2nd script starting' && ${THIS_SH@Q} ${sub3@Q}" >"$sub2"
        echo "echo '3rd script starting'" >"$sub3"

        . "$sub1"

Turns out the best time to find bugs in your code is when demoing it for 
someone else. :-)


On 12/22/22 11:18 AM, Chet Ramey wrote:
> On 12/21/22 11:44 PM, Oğuz wrote:
> > 22 Aralık 2022 Perşembe tarihinde Dan Church <h3xx@gmx.com> yazdı:
> > > Repro:
> > >
> > >     sub1=$(mktemp)
> > >     sub2=$(mktemp)
> > >     sub3=$(mktemp)
> > >
> > >     echo '( echo "1st script executing" ; . '"$sub2"' ; echo "1st 
> > > script
> > > still executing" )' >"$sub1"
> > >     echo 'echo "2nd script starting" && ${THIS_SH} '"$sub3" >"$sub2"
> > >     echo 'echo "3rd script starting"' >"$sub3"
> > >
> > >     . "$sub1"
> > >
> > > "1st script still executing" will never be printed.
> >
> > Or
> >
> >      $ bash -c '(. <(echo ": && uname"); echo x)'
> >      Linux
> >      $
> >
> > x is never printed. Looks like another bug caused by aggressive subshell
> > optimizations
>
> Thanks for the reports, both of you. I've attached a patch.
>
> Chet
--

Regards,
Dan Church
🌎 web: h3xx.codeberg.page <https://h3xx.codeberg.page/>
"If I am to be judged by those who come after me, let me be judged for 
the truth." — Raistlin Majere