Re: [PATCH 2/3] t5615: avoid re-using descriptor 4

From: Jeff King <peff@peff.net>
Date: Oct 19, 2017, 23:23 UTC
Message-ID: <20171019232337.zfd7occtjboem7f4@sigill.intra.peff.net>
In-Reply-To: <CAGZ79kYTmUnM+fcf222-cvwB3Fg4+J_xy28E7A3AYryx4qDf_w@mail.gmail.com>

On Thu, Oct 19, 2017 at 02:46:33PM -0700, Stefan Beller wrote:

Show 16 quoted lines

> > I also considered trying to bump the "set -x" output descriptor to "9".
> > That just moves the problem around, but presumably scripts are less
> > likely to go that high. :)
> >
> > It would also be possible to pick something insanely high, like "999".
> > Many shells choke on descriptors higher than 9, but since the issue is
> > related to BASH_XTRACEFD, we could make it a bash-only thing. I don't
> > know if it's worth the trouble. I hate leaving a subtle "don't use
> > descriptor 4 in a subshell or your script will break" hand-grenade like
> > this lying around, but we do seem to have only one instance of it over
> > the whole test suite.
> 
> I would imagine that a higher fd for BASH_XTRACEFD
> would be less explosive than requiring the tests to skip
> the low number 4. (It is not *that* low. In e.g. git-submodule.sh
> we make use of 3 in cmd_foreach, not needing more.)

So one trick is that we can't just set it to a higher number. We have to also open and manage that descriptor. It might be enough to do:

  if test -n "$BASH_VERSION"
  then
	exec 999>&4
	BASH_XTRACEFD=999
  fi

but since we fiddle with descriptors on a per-test basis, I'm not sure if that's it or not. I think for convincing output to go to it, it probably is. We tend to point things _at_ descriptor 4, not point descriptor 4 elsewhere. But the fix in patch 1 is an exception, where we try to suppress the "set +x" output. For that we have to redirect 999, too (which is hard because ">&999" is syntactically invalid in other shells, so we have to follow a separate code path for bash or get into evals).

Or start playing games with unsetting BASH_XTRACEFD (which closes 999, and then we re-open 999>&4 and reset XTRACEFD).

I think it might be workable, but I'm worried we're opening a can of worms. Or continuing to dig into the can of worms from the original BASH_XTRACEFD, if you prefer. :)

-Peff