Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt
-DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/bin'
-DSTANDARD_UTILS_PATH='/usr/bin' -DSYS_BASHRC='/etc/ba
On Sun, Jul 25, 2021 at 07:09:50PM +0200, andrej--- via Bug reports for the GNU
Bourne Again SHell wrote:
> Description:
> An extglob like +(!(x))y causes Bash to freeze with a 100% CPU
> utilization.
> At the first glance the freeze doesn't seem to depend on the
> (non-)existence of
On Jul 25 2021, Greg Wooledge wrote:
> On Sun, Jul 25, 2021 at 07:09:50PM +0200, andrej--- via Bug reports for the
> GNU Bourne Again SHell wrote:
>> Description:
>> An extglob like +(!(x))y causes Bash to freeze with a 100% CPU
>> utilization.
>> At the first glance the freeze doesn't
On 7/25/21 1:09 PM, andrej--- via Bug reports for the GNU Bourne Again
SHell wrote:
Bash Version: 5.1
Patch Level: 8
Release Status: release
Description:
An extglob like +(!(x))y causes Bash to freeze with a 100% CPU
utilization.
At the first glance the freeze doesn't seem to
On Jul 25 2021, Chet Ramey wrote:
> In the bash build directory, for instance, it fails right away, as it
> should: there aren't any files ending in `y'.
It doesn't matter whether the file name contains `y', just how long it
is. Try creating a file with a name of 30 or more characters. Each
add
On 7/25/21 5:01 PM, Andreas Schwab wrote:
On Jul 25 2021, Chet Ramey wrote:
In the bash build directory, for instance, it fails right away, as it
should: there aren't any files ending in `y'.
It doesn't matter whether the file name contains `y', just how long it
is.
That's not what I mean
