Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS: -O2 -pipe -march=native -ggdb3
uname output: Linux 2021-10-24 5.15.34-gentoo-dist-hardened #1 SMP Sat Apr 16
02:20:51 BST 2022 x86_64 AMD Ryzen 9
> > #!/bin/bash
> > : $((08 + 0)); exit
> > echo "Should not get here."
>
> It never executes `exit'.
>
> The explanation in
> https://lists.gnu.org/archive/html/bug-bash/2022-04/msg00010.html applies
> here.
>
> The arithmetic syntax error (invalid octal constant) results in a word
> expansio
On 4/15/22 12:57 PM, Frank Heckenbach wrote:
Bash Version: 5.1
Patch Level: 16
Release Status: release
Description:
bash executes statement after "exit".
Happens with or without "set -e".
Doesn't happen with newline instead of ";".
Similar to https://bugs.debian.org/819327, but perhaps not
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 mars 5.10.0-12-amd64 #1 SMP Debian 5.10.103-1 (2022-03-07)
x86_64 GNU/Lin
On Apr 15 2022, Martin Schulte wrote:
> I would either have expected to get PS2 and no error messages after
> entering the line starting with sleep
That's what I get when trying this in 5.2-beta.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73
Hello bash-bughunters,
please consider the following interactive lines:
$ echo $BASH_VERSION
5.1.4(1)-release
$ uname -a
Linux t1 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux
$ echo $BASH_VERSION
5.1.4(1)-release
$ sleep $(expr 60 - $(date +%s')) ; date
bash: command su
