> On Mon, Jan 8, 2024, 12:26 wrote:
>
>> Do any of the other six patches in that report also apply to Bash 5.2?
>>
>
> Yes, all but the one for the `kv' builtin which did not exist yet. See
> attached.
>
>>
>>
Would you please consider releasing these as an official patch?
On Mon, Jan 15, 2024, 19:03 Chet Ramey wrote:
> On 1/11/24 7:29 PM, Ángel wrote:
> > On 2024-01-11 at 09:29 -0500, Chet Ramey wrote:
> >> On 1/11/24 2:37 AM, ilya Basin wrote:
> >>> Dear.
> >>> I needed to read 16 bytes from a binary file and tried to replace a
> >> hexdump call with read built-i
On 1/11/24 7:29 PM, Ángel wrote:
On 2024-01-11 at 09:29 -0500, Chet Ramey wrote:
On 1/11/24 2:37 AM, ilya Basin wrote:
Dear.
I needed to read 16 bytes from a binary file and tried to replace a
hexdump call with read built-in. I expected that with "-N1" if a NUL
character is encountered bash wo
On 1/14/24 7:24 PM, Grisha Levit wrote:
See also (even after the fix pushed today):
bash -c '(( X=([))])'
heap-use-after-free parse.y:2712:60 in shell_getc
bash -c '(( X=([))]) ))'
heap-use-after-free parse.y:2077:11 in parser_expanding_alias
Thanks. This is a different i
2024年1月15日(月) 23:02 :
> Description:
> Found while editing history line with a find pattern.
> Apparently bash doesn't like + characters very much.
>
> Repeat-By:
> find . -type f -ctime +30 ! -ctime +40 -exec ls -la --full-time {} +
> Move cursor to any point after
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall
uname output: Linux sourcetronic.com 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2
(2022-10-21) x8
