Re: 'wait -n' with and without id arguments

2024-08-30 Thread Zachary Santer
CWRU/CWRU.chlog: >8/26 > > execute_cmd.c > [...] > - execute_connection: in default mode, bash performs jobs notifications > in an interactive shell between commands separated by ';' or '\n'. > It shouldn't do this in posix mode, since posix now specifies when > notifications can

Re: bash passes changed termios to backgrounded process(es) groups?

2024-08-30 Thread Steffen Nurpmeso
Chet Ramey wrote in : |On 8/29/24 2:17 PM, Robert Elz wrote: |> Date:Thu, 29 Aug 2024 10:40:25 -0400 |> From:Chet Ramey |> Message-ID: |> |>| It's not a big problem. You're in the background if your process \ |>| group is |>| not equal to the terminal's p

Re: bash - reproducible SEGFAULT on rapid SIGINTs

2024-08-30 Thread Chet Ramey
On 8/30/24 5:05 AM, Eduardo A. Bustamante López wrote: On Wed, Aug 28, 2024 at 01:16:57PM +0200, Tycho Kirchner wrote: Hi, Sending rapid SIGINTs from another shell quickly results in a SEGFAULT of the bash instance receiving them. Steps to reproduce: * Open up a shell SHELL_1 and record its pid

Re: bash - reproducible SEGFAULT on rapid SIGINTs

2024-08-30 Thread Chet Ramey
On 8/28/24 7:16 AM, Tycho Kirchner wrote: Hi, Sending rapid SIGINTs from another shell quickly results in a SEGFAULT of the bash instance receiving them. Steps to reproduce: * Open up a shell SHELL_1 and record its pid, e.g. "echo $$" * Launch another shell and send rapid SIGINTs: while true ;

Re: [PATCH 1/2] printf: fix heap buffer overflow in printf_builtin

2024-08-30 Thread Martin D Kealey
Hi Andrei Ok, I see the problem. This fault is triggered when the format string has '%(' but is missing the closing ')' - so the entire remainder of the format string is tentatively recorded as the time-format substring. This line: if (*++fmt != 'T') should be changed to: if (n > 0 || *

Re: bash - reproducible SEGFAULT on rapid SIGINTs

2024-08-30 Thread Chet Ramey
On 8/28/24 7:16 AM, Tycho Kirchner wrote: Hi, Sending rapid SIGINTs from another shell quickly results in a SEGFAULT of the bash instance receiving them. Steps to reproduce: * Open up a shell SHELL_1 and record its pid, e.g. "echo $$" * Launch another shell and send rapid SIGINTs: while true ;

Re: Patch to unify shopt & set-o

2024-08-30 Thread Chet Ramey
On 8/29/24 1:58 AM, Martin D Kealey wrote: Hi Chet On Wed, 28 Aug 2024 at 23:58, Chet Ramey > wrote: On 8/24/24 1:46 PM, Martin D Kealey wrote: > I've been making some tentative patches to the `devel` branch, and since I > have a fairly large bashr

Re: bash passes changed termios to backgrounded process(es) groups?

2024-08-30 Thread Chet Ramey
On 8/29/24 4:59 PM, Martin D Kealey wrote: On Fri, 30 Aug 2024 at 04:17, Robert Elz > wrote: SIGTTOU is also sent, unconditionally, by any attempt to change any of the terminal's attributes, and the process (group) (by default) stops. (I don't recall off

Re: bash passes changed termios to backgrounded process(es) groups?

2024-08-30 Thread Chet Ramey
On 8/29/24 2:17 PM, Robert Elz wrote: Date:Thu, 29 Aug 2024 10:40:25 -0400 From:Chet Ramey Message-ID: | It's not a big problem. You're in the background if your process group is | not equal to the terminal's process group. That's more or less sufficient

Re: [PATCH 1/2] printf: fix heap buffer overflow in printf_builtin

2024-08-30 Thread Андрей Ковалёв
Hi there! I completely understand your point of view. Although I made a few mistakes when writing the patch, I wrote patch for a reason. I was doing fuzzing testing in bash4, and at some point during fuzzing, ASAN (AddressSanitizer) was launched. This problem also existed in the master branch

Re: bash - reproducible SEGFAULT on rapid SIGINTs

2024-08-30 Thread Eduardo A . Bustamante López
On Wed, Aug 28, 2024 at 01:16:57PM +0200, Tycho Kirchner wrote: > Hi, > Sending rapid SIGINTs from another shell quickly results in a SEGFAULT of the > bash instance receiving them. Steps to reproduce: > * Open up a shell SHELL_1 and record its pid, e.g. "echo $$" > * Launch another shell and send