On 1/2/22 1:38 PM, Frank Heckenbach wrote:
Chet Ramey wrote:
On 1/1/22 7:02 PM, Frank Heckenbach wrote:
Thanks for the report. This is a pretty good in-depth analysis of the issue.
This was fixed back in March, 2021 in the devel branch as a result of
https://savannah.gnu.org/patch/?10035 (though the fix is different from
yours).
It's queued up as one of the next set of bash-5.1 patches.
I'm not happy with the way this bug is handled.
That is, as always, your privilege.
After all, we're talking about silent data corruption, and now I
learn the bug is known for almost a year, the fix is known and still
hasn't been released, not even as an official patch.
If you use the number of bug reports as an indication of urgency, this is
rarely encountered. Yours is the second (maybe the third?) report.
In the meantime, the buggy version has made it into a Debian stable
release (and I assume many other distributions) and caused me (and I
assume many other users) a lot of trouble.
I wouldn't make any assumptions beyond your own experience.
I spend many hours, first debugging my own script, then bash, which
could have been spent more productively!
I appreciate that you did.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
