Jan 6, 2024, 23:59 by grishale...@gmail.com:

>
>
> On Sun, Jan 7, 2024, 00:26 pourko--- via Bug reports for the GNU Bourne Again 
> SHell <> bug-bash@gnu.org> > wrote:
>
>> For demonstration, put a $(<file) construct inside a loop, and the leak 
>> becomes very noticeable:
>>
>
>
>> The bug is not present in bashes before 5.2.0.
>>
>
> I believe this is fixed in (yet unreleased) Bash 5.3. See report [1] applied 
> in [2].
>
>  [1]:  > https://lists.gnu.org/archive/html/bug-bash/2023-06/msg00045.html
>  [2]:  > 
> https://git.savannah.gnu.org/cgit/bash.git/diff/builtins/evalstring.c?h=devel&id=81f7b44564cd1510788035cea7c59631865a7db2&dt=1#n766
>

Could we maybe get a patch for the 5.2 series?

It's unclear when stable distros will start shipping with 5.3, and reverting to 
5.1 is not a pleasant alternative.



  • Bash 5.2.0: Memo... pourko--- via Bug reports for the GNU Bourne Again SHell
    • Re: Bash 5.2... Grisha Levit
      • Re: Bash... pourko--- via Bug reports for the GNU Bourne Again SHell
        • Re: ... Chet Ramey
        • Re: ... pourko--- via Bug reports for the GNU Bourne Again SHell
          • ... Grisha Levit
            • ... pourko--- via Bug reports for the GNU Bourne Again SHell
          • ... pourko--- via Bug reports for the GNU Bourne Again SHell
            • ... Chet Ramey
      • Re: Bash... Chet Ramey
    • Re: Bash 5.2... pourko--- via Bug reports for the GNU Bourne Again SHell

Reply via email to