willi1337 bald writes:
> A deeply nested and incorrect regex expression can cause exhaustion of
> stack resources, which crashes the bash process.
Further, you could construct a deeply nested regex that is correct but
would still crash the process. It's hard to define what should happen
in a way
On 3/30/22 7:48 PM, Steffen Nurpmeso wrote:
Chet Ramey wrote in
:
|On 3/30/22 11:16 AM, willi1337 bald wrote:
|> Bash Version: 5.1
|> Patch Level: 16
|> Release Status: release
|>
|> Description:
|>
|> A deeply nested and incorrect regex expression can cause exhaustion of
|> s
Chet Ramey wrote in
:
|On 3/30/22 11:16 AM, willi1337 bald wrote:
|> Bash Version: 5.1
|> Patch Level: 16
|> Release Status: release
|>
|> Description:
|>
|> A deeply nested and incorrect regex expression can cause exhaustion of
|> stack resources, which crashes the bash process.
|
|B
On 3/30/22 11:16 AM, willi1337 bald wrote:
> Bash Version: 5.1
> Patch Level: 16
> Release Status: release
>
> Description:
>
> A deeply nested and incorrect regex expression can cause exhaustion of
> stack resources, which crashes the bash process.
Bash doesn't use it's own regexp engine; it u
On Wed, Mar 30, 2022 at 7:47 PM Martin Schulte
wrote:
> Hello Willi!
>
> > Fix:
> > Count the stack frames during recursive parsing and emit error before
> stack
> > resources are entirely consumed.
>
> What exactly should happen and what is the benefit of this solution?
>
i guess it wont segfau
Hello Willi!
> Fix:
> Count the stack frames during recursive parsing and emit error before stack
> resources are entirely consumed.
What exactly should happen and what is the benefit of this solution?
BTW: I tried
trap 'echo "Ohohoh..."; exit 1;' SIGSEGV
but the signal wasn't caught (which di
