On Fri, Dec 19, 2025, 17:44 anushakov--- via Bug reports for the GNU Bourne
Again SHell <[email protected]> wrote:
> Dear Bash Maintainers,
>
> I encountered an issue in Bash and would like to report it. crash2.txt
> is attached to the email.
>
> Steps to reproduce
> $ CC=clang-19 CFLAGS=" -g -fsanitize=address -Wno-everything
> -std=gnu99 " ./configure --enable-largefile --without-bash-malloc
> $ make
> $ cat crash2.txt | xarg -0 ./bash
>
>
> Steps to generate crash2.txt:
> copy the text into file bs64.txt (between 1. = and 2.=)
> 1.=====================================================================
> =======================
> LWMAJHtQQRs9PT1//28gZnV732VjaG8gZnVuY3R7bmN0ey11b247IH07/x51dGUKCvstQDw
> 8cnUA
> bltbW1tbW1tbW1tbW1tbW1tbW1s9W1tlc10ASEheAA==
> 2.=====================================================================
> =======================
> Then do the action:
> base64 -d bs64.txt > crash2.txt
>
Here's a simpler reproducer:
bash -c $'${}\n<<X'
>
