Linda Walsh wrote:
> Am running an older bash version and this may be fixed (assuming it
> is a bug and I'm not confused...:-))
>
> bash version = 3.2.39(20)
>
> This works:
> 1)if [ -n "" -a 2 -gt 1 ] ; then echo one;fi
>
> This does not:
> 2)if [[ -n "" -a 2 -gt 1 ]] ; then echo on
Am running an older bash version and this may be fixed (assuming it
is a bug and I'm not confused...:-))
bash version = 3.2.39(20)
This works:
1) if [ -n "" -a 2 -gt 1 ] ; then echo one;fi
This does not:
2) if [[ -n "" -a 2 -gt 1 ]] ; then echo one;fi
Shouldn't 2 work equally w
Roman Rakus writes:
> diff -up bash-3.2/lib/readline/signals.c.rr bash-3.2/lib/readline/signals.c
> --- bash-3.2/lib/readline/signals.c.rr2009-01-19 15:57:29.0
> +0100
> +++ bash-3.2/lib/readline/signals.c 2009-01-19 16:00:04.0 +0100
> @@ -111,11 +111,19 @@ static sigha
It's possible to make bash locked up. It's done by bad signal handling
in bash and/or readline. It may happened when bash/readline catch signal
in any alloc call. I have changed readline to process signals only in
safe point. This appears also in bash-4. I will attach a small
reproducer (normal
