bug-bash  

Messages by Thread

• Bash 5.3 bug - POSIX process substitution $() handling error with embedded comments Jari Aalto
  • Re: Bash 5.3 bug - POSIX process substitution $() handling error with embedded comments Robert Elz
  • Re: Bash 5.3 bug - POSIX process substitution $() handling error with embedded comments Chet Ramey
• [bug #67957] Syntax error messages permanently change after interrupting process/command substitution parsing anonymous
• "echo $((0x))" is accepted, treated as 0x0 Denys Vlasenko
  • Re: "echo $((0x))" is accepted, treated as 0x0 Andreas Kähäri
  • Re: "echo $((0x))" is accepted, treated as 0x0 Martin D Kealey
  • Re: "echo $((0x))" is accepted, treated as 0x0 Denys Vlasenko
  • Re: "echo $((0x))" is accepted, treated as 0x0 Chet Ramey
  • Re: "echo $((0x))" is accepted, treated as 0x0 Andreas Schwab
  • Re: "echo $((0x))" is accepted, treated as 0x0 Chet Ramey
  • Re: "echo $((0x))" is accepted, treated as 0x0 Robert Elz
  • Re: "echo $((0x))" is accepted, treated as 0x0 Andreas Kähäri
  • Re: "echo $((0x))" is accepted, treated as 0x0 Robert Elz
  • Re: "echo $((0x))" is accepted, treated as 0x0 Chet Ramey
• bash src mirror at https://github.com/bminor/bash.git gone? Cedric Blancher
  • Re: bash src mirror at https://github.com/bminor/bash.git gone? Koichi Murase
  • Re: bash src mirror at https://github.com/bminor/bash.git gone? Cedric Blancher
  • Re: bash src mirror at https://github.com/bminor/bash.git gone? Oğuz
  • Re: bash src mirror at https://github.com/bminor/bash.git gone? Andreas Schwab
• ${ ...; } can end up closing user fds open within Stephane Chazelas
  • Re: ${ ...; } can end up closing user fds open within Chet Ramey
• man history correction Martin F.
  • Re: man history correction Chet Ramey
• [bug #67928] Typo in bash man page anonymous
• segfault after redefining an alias as a function Jason Puschnig
  • Re: segfault after redefining an alias as a function Greg Wooledge
  • Re: segfault after redefining an alias as a function Martin D Kealey
• history -r should print error message if file doesn't exist Dan Jacobson
  • Re: history -r should print error message if file doesn't exist Chet Ramey
  • Re: history -r should print error message if file doesn't exist Stan Marsh
  • Re: history -r should print error message if file doesn't exist Ángel
  • Re: history -r should print error message if file doesn't exist Chet Ramey
• time builtin: incorrect formatting (e.g. 0m28.:00s) Nikola Beneš
  • Re: time builtin: incorrect formatting (e.g. 0m28.:00s) Andrew Church
  • Re: time builtin: incorrect formatting (e.g. 0m28.:00s) Chet Ramey
• Bash 5.3: configure fix Marc Aurèle La France
  • Re: Bash 5.3: configure fix Chet Ramey
• Problems encountered with printing local variables in the new command substitution in bash 5.3 王伟
  • Re: Problems encountered with printing local variables in the new command substitution in bash 5.3 Greg Wooledge
• Bash 5.3 ARRAY_EXPORT build fix Marc Aurèle La France
  • Re: Bash 5.3 ARRAY_EXPORT build fix Chet Ramey
  • Re: Bash 5.3 ARRAY_EXPORT build fix Marc Aurèle La France
  • Re: Bash 5.3 ARRAY_EXPORT build fix Marc Aurèle La France
• [PATCH] Fix interaction between shell history and case-in-comsub Jason Wilkes
• A Bug in History letshaveanadventure
  • Re: A Bug in History Jason Wilkes
• `wait` triggers an infinite loop when used in an EXIT trap Aleksey Covacevice
  • Re: `wait` triggers an infinite loop when used in an EXIT trap Chet Ramey
  • Re: `wait` triggers an infinite loop when used in an EXIT trap Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: `wait` triggers an infinite loop when used in an EXIT trap Chet Ramey
  • Re: `wait` triggers an infinite loop when used in an EXIT trap Robert Elz
  • Re: `wait` triggers an infinite loop when used in an EXIT trap Chet Ramey
  • Re: `wait` triggers an infinite loop when used in an EXIT trap Robert Elz
  • Re: `wait` triggers an infinite loop when used in an EXIT trap Chet Ramey
  • Re: `wait` triggers an infinite loop when used in an EXIT trap Robert Elz
• Correction in documentation Anshuman Khanna
  • Re: Correction in documentation Greg Wooledge
  • Re: Correction in documentation Anshuman Khanna
• Length gotten from references to an value of an array is always 0 Ore Redstone
  • Re: Length gotten from references to an value of an array is always 0 Martin D Kealey
  • Re: Length gotten from references to an value of an array is always 0 Chet Ramey
• Segmentation fault after a script runs source on itself Parker Macdonald (Student)
  • Re: Segmentation fault after a script runs source on itself Robert Elz
• Question about associative array runtime assignment vs literal initialization 王伟
  • Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
  • Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
  • Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
  • Re: Question about associative array runtime assignment vs literal initialization Zachary Santer
  • Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
  • Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
  • Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
  • Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
  • Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
  • Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
  • Re: Question about associative array runtime assignment vs literal initialization Zachary Santer
  • Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
  • Re: Question about associative array runtime assignment vs literal initialization Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
  • Re: Question about associative array runtime assignment vs literal initialization Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: Question about associative array runtime assignment vs literal initialization Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
  • Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
  • Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
  • Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
  • Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
  • Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
  • Re: Question about associative array runtime assignment vs literal initialization Greg Wooledge
  • Re: Question about associative array runtime assignment vs literal initialization Chet Ramey
  • Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
  • Re: Question about associative array runtime assignment vs literal initialization Koichi Murase
• heap-use-after-free buffered_getchar() input.c:611:11 anushakov--- via Bug reports for the GNU Bourne Again SHell
  • Re: heap-use-after-free buffered_getchar() input.c:611:11 Chet Ramey
• signed integer overflow ipow() bash/expr.c:954:12 anushakov--- via Bug reports for the GNU Bourne Again SHell
  • Re: signed integer overflow ipow() bash/expr.c:954:12 Collin Funk
  • Re: signed integer overflow ipow() bash/expr.c:954:12 Chet Ramey
• heap-use-after-free executing_line_number() bash/execute_cmd.c:437:40 anushakov--- via Bug reports for the GNU Bourne Again SHell
  • Re: heap-use-after-free executing_line_number() bash/execute_cmd.c:437:40 Grisha Levit
  • Re: heap-use-after-free executing_line_number() bash/execute_cmd.c:437:40 Duncan Roe
  • Re: heap-use-after-free executing_line_number() bash/execute_cmd.c:437:40 Chet Ramey
• A 'password' mode? (Was: RFE: Echo dots option for 'read -s') Stan Marsh
• BadInstruction ansicstr() strtrans.c:147:14 anushakov--- via Bug reports for the GNU Bourne Again SHell
  • Re: BadInstruction ansicstr() strtrans.c:147:14 Chet Ramey
• vi-mode 'v' does not reset parser state after fc execution William Pursell
  • Re: vi-mode 'v' does not reset parser state after fc execution Chet Ramey
  • Re: vi-mode 'v' does not reset parser state after fc execution Chet Ramey
  • vi-mode 'v' does not reset parser state after fc execution Stan Marsh
• Re: AI slop (Was: Feature request: blah, blah, blah...) Stan Marsh
• Feature request: Make bash do NUL separation natively oliver . hinck
  • Re: Feature request: Make bash do NUL separation natively Eric Cook
  • Re: Feature request: Make bash do NUL separation natively Greg Wooledge
• Piping wc causes error Kye Hunter
  • Re: Piping wc causes error Greg Wooledge
  • Re: Piping wc causes error Kye Hunter
  • Re: Piping wc causes error Chet Ramey
  • Re: Piping wc causes error Kye Hunter
• (strace added) fedora42: running `gawk` permanently corrupts shell FD 0/1 | cat: -: input file is output file bug-bash
• fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file bug-bash
  • Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Grisha Levit
  • Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Chet Ramey
  • Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Robert Elz
  • Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file G. Branden Robinson
  • Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Grisha Levit
  • Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Chet Ramey
  • Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Chet Ramey
  • Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file bug-bash
  • Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Robert Elz
  • Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Robert Elz
  • Re: fedora42: running `gawk` permanently corrupts shell file descriptors (FD 0/1) | cat: -: input file is output file Chet Ramey
• RFE: Echo dots option for 'read -s' Bruce Jerrick
  • Re: RFE: Echo dots option for 'read -s' Martin D Kealey
  • Re: RFE: Echo dots option for 'read -s' Martin D Kealey
  • Re: RFE: Echo dots option for 'read -s' Martin D Kealey
  • Re: RFE: Echo dots option for 'read -s' Chet Ramey
  • Re: RFE: Echo dots option for 'read -s' Bruce Jerrick
  • Re: RFE: Echo dots option for 'read -s' Chet Ramey
  • Re: RFE: Echo dots option for 'read -s' Robert Elz
  • Re: RFE: Echo dots option for 'read -s' Chet Ramey
  • Re: RFE: Echo dots option for 'read -s' Martin D Kealey
  • Re: RFE: Echo dots option for 'read -s' Robert Elz
  • Re: RFE: Echo dots option for 'read -s' Chet Ramey
  • Re: RFE: Echo dots option for 'read -s' Martin D Kealey
  • Re: RFE: Echo dots option for 'read -s' Chet Ramey
  • Re: RFE: Echo dots option for 'read -s' Oğuz
  • Re: RFE: Echo dots option for 'read -s' Stan Marsh
  • Re: RFE: Echo dots option for 'read -s' Stan Marsh
  • Re: RFE: Echo dots option for 'read -s' Greg Wooledge
  • Re: RFE: Echo dots option for 'read -s' Martin D Kealey
  • Re: RFE: Echo dots option for 'read -s' Chet Ramey
  • Re: RFE: Echo dots option for 'read -s' Chet Ramey
  • Re: RFE: Echo dots option for 'read -s' Stan Marsh
  • Re: RFE: Echo dots option for 'read -s' Chet Ramey
• slight tweak to Patch-ID: bash53-009 Dennis Clarke via Bug reports for the GNU Bourne Again SHell
  • Re: slight tweak to Patch-ID: bash53-009 Chet Ramey
• Bash-5.3 Official patch 9 Chet Ramey
• [bug #67782] bash split $() for array initialization but not for associative array initialization anonymous
  • Re: [bug #67782] bash split $() for array initialization but not for associative array initialization Léa Gris
  • Re: [bug #67782] bash split $() for array initialization but not for associative array initialization Chet Ramey
  • Re: [bug #67782] bash split $() for array initialization but not for associative array initialization Greg Wooledge
  • Re: [bug #67782] bash split $() for array initialization but not for associative array initialization Chet Ramey
  • Re: [bug #67782] bash split $() for array initialization but not for associative array initialization Zachary Santer
  • Re: [bug #67782] bash split $() for array initialization but not for associative array initialization Stan Marsh
• [PATCH] input: Reset O_NONBLOCK in buffered read as well Keno Fischer
  • Re: [PATCH] input: Reset O_NONBLOCK in buffered read as well Chet Ramey
• Seconds and microseconds? Stan Marsh
  • Re: Seconds and microseconds? Greg Wooledge
• Seconds and microseconds? (Was: Philosophical bash(1) bug) Stan Marsh
  • Re: Seconds and microseconds? (Was: Philosophical bash(1) bug) Eduardo Bustamante
  • Re: Seconds and microseconds? (Was: Philosophical bash(1) bug) Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: Seconds and microseconds? (Was: Philosophical bash(1) bug) Félix Hauri via Bug reports for the GNU Bourne Again SHell
  • Re: Seconds and microseconds? (Was: Philosophical bash(1) bug) Léa Gris
• Philosophical bash(1) bug Martin Wheatley
  • Re: Philosophical bash(1) bug Chet Ramey
  • Re: Philosophical bash(1) bug Zachary Santer
  • Re: Philosophical bash(1) bug Oğuz
  • Re: Philosophical bash(1) bug Léa Gris
  • Re: Philosophical bash(1) bug Oğuz
  • Re: Philosophical bash(1) bug Léa Gris
  • Re: Philosophical bash(1) bug Chet Ramey
  • Re: Philosophical bash(1) bug Robert Elz
  • Re: Philosophical bash(1) bug Greg Wooledge
  • Re: Philosophical bash(1) bug Andreas Kähäri
  • Re: Philosophical bash(1) bug Chet Ramey
  • Re: Philosophical bash(1) bug Chet Ramey
  • Re: Philosophical bash(1) bug Chet Ramey
  • Re: Philosophical bash(1) bug Stan Marsh
• [bug #67756] UndefinedBehavior in brace_expand Leonid Reviakin
• [bug #67755] heap-buffer-overflow (write 1 byte) in brace_expand function anonymous
• [sr #111350] problems using date in .bash_profile anonymous
  • Re: [sr #111350] problems using date in .bash_profile Stan Marsh
• [bug #67745] trap EXIT race in subshell produces inconsistent results oxumbead
• Bash fails to compile with GCC 15 / C23 due to bool typedef in bashansi.h hao a
  • Re: Bash fails to compile with GCC 15 / C23 due to bool typedef in bashansi.h Martin D Kealey
  • Re: Bash fails to compile with GCC 15 / C23 due to bool typedef in bashansi.h Chet Ramey
  • Re: Bash fails to compile with GCC 15 / C23 due to bool typedef in bashansi.h Chet Ramey
• Incompatibility of quoting ampersand in substitution [email protected]
  • Re: Incompatibility of quoting ampersand in substitution Chet Ramey
  • Re: Incompatibility of quoting ampersand in substitution Chet Ramey
• Bash-5.3 Official patch 8 Chet Ramey
• Bash-5.3 Official patch 7 Chet Ramey

• Earlier messages