As such bugs are likely related to buffer issues, maybe even in
underlying APIs, and since they only surface after very lengthy
mysterious sequences of commands - often just on single specific system
installations - I wouldn't know how you can reproduce this in a test.
Maybe you have specific testing frameworks for this, that would reduce
the whole script to more basic components and which schematically remove
or add complexity until the nature of the bug becomes more apparent?
This seems to call for a specialist who is able to follow the problem
into a far lower level of abstraction.
As it stands now, I don't see how there is no way how this kind of
execution can make any sense from a scripting POV.
Of course in a giant script, all sorts of random things might happen.
But this is not one of them.
On 1/21/21 10:38 PM, Chet Ramey wrote:
On 1/21/21 4:27 PM, Mathias Steiger wrote:
No.
If you read the the rest of the bug report, it might become clearer
to you.
Suppose I wrote a simple script:
{if echo "27ac5e2f757302" >& /dev/null; then echo "yes"; else
echo "no"; fi } > output
Suppose you did.
I did, after correcting the syntax errors in yours, and couldn't
reproduce
the problem. So if you can extract a script that exhibits the problem
from
the rest of the autoconf framework, I'll be glad to see if it
demonstrates
a bug in bash.
