Re: Bash 5.2.21 segfaults when I feed it garbage

2024-01-08 Thread Chet Ramey
On 1/8/24 12:10 AM, Nathan Mills wrote: Bash Version: 5.2 Patch Level: bash-5.2-22-g4b0f8ba2 Release Status: master Description: Bash 5.2 segfaults when I run the following crashing input (See Repeat-By:). Thanks for the report and detailed diagnosis, and the reproducer. Your fix,

Re: Bash 5.2.0: Memory leak with $(

2024-01-08 Thread pourko--- via Bug reports for the GNU Bourne Again SHell
Jan 8, 2024, 09:23 by chet.ra...@case.edu: > > *** ../bash-5.2-patched/builtins/evalstring.c Tue Dec 13 12:53:21 2022 > --- builtins/evalstring.c Tue Nov 28 17:25:39 2023 > *** > *** 763,766 > --- 773,779 > if (fnp) > *fnp = fn; > + else > + free (fn); > + >

Re: wait skips signals but first one

2024-01-08 Thread Chet Ramey
On 1/5/24 2:46 PM, Mykyta Dorokhin wrote: Bash Version: 5.1 Patch Level: 16 Release Status: release Description: I'm working on a custom project within the Yocto framework. After a recent build system update, the bash version updated to 5.1.16. Subsequently, I've noticed peculiar side

bash-4-2 issue

2024-01-08 Thread Sam Kappen via Bug reports for the GNU Bourne Again SHell
Hi, We see that bash throws the "Operation not permitted" error when doing chained pipe operation along with a debug trap. We set a debug trap here "my_debug" to save the terminal commands entered. The GNU bash, version used is 4.2. root@freescale-p2020ds:~/dir# ls -l | grep a | grep b | grep

Bash 5.2.21 segfaults when I feed it garbage

2024-01-08 Thread Nathan Mills
From: Nathan Mills To: bug-bash@gnu.org Subject: Bash 5.2.21 segfaults when I feed it garbage Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: clang-15.0.7 Compilation CFLAGS: -g -O2 uname output: Linux MSI

Re: Bash 5.2.0: Memory leak with $(

2024-01-08 Thread Chet Ramey
On 1/7/24 12:59 AM, Grisha Levit wrote: On Sun, Jan 7, 2024, 00:26 pourko--- via Bug reports for the GNU Bourne Again SHell wrote: For demonstration, put a $( 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

Re: Bash 5.2.0: Memory leak with $(

2024-01-08 Thread Chet Ramey
On 1/7/24 1:17 AM, pourko--- via Bug reports for the GNU Bourne Again SHell wrote:  [2]:  > https://git.savannah.gnu.org/cgit/bash.git/diff/builtins/evalstring.c?h=devel=81f7b44564cd1510788035cea7c59631865a7db2=1#n766 Could we maybe get a patch for the 5.2 series? ***