Loop within trap handling

2018-03-28 Thread werner
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-suse-linux-gnu' -DCONF_VENDOR='suse' -DLOCALEDIR='/usr/share/locale' -DP

Strange behaviour when sending SIGTERM to bash

2018-03-28 Thread Martin Schulte
Hello, I'm running bash under Debian Stretch: $ echo $BASH_VERSION 4.4.12(1)-release $ trap $ echo $$ 1100 $ kill 1100 $ => Looks fine for me Then I do a kill 1100 from another session and the bash above terminates. => Looks wrong for me Greetings, Martin

command_not_found_handle strange behaviour

2018-03-28 Thread Кириллов Дима
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/local

important bug

2018-03-28 Thread Klaus Bartels
If you execute the following script the result is wrong. It is self explaining: --- # # GNU bash, version 4.4.12(1)-release (x86_64-slackware-linux-gnu) # Linux ... 4.9.31 #1 SMP Wed Jun 7 14:57:36 CDT 2017 x86_64 Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz GenuineIntel G

Re: important bug

2018-03-28 Thread Greg Wooledge
On Wed, Mar 28, 2018 at 08:22:16PM +0200, Klaus Bartels wrote: > If you execute the following script the result is wrong. It is self > explaining: > --- > # > # GNU bash, version 4.4.12(1)-release (x86_64-slackware-linux-gnu) > # Linux ... 4.9.31 #1 SMP Wed Jun 7 14:57:3

Re: important bug

2018-03-28 Thread Eric Blake
On 03/28/2018 01:22 PM, Klaus Bartels wrote: If you execute the following script the result is wrong. It is self explaining: Sorry, but your script behaves as documented by POSIX. It is not a bug in bash, but in your expectations. --- # # GNU bash, version 4.4.1

Re: important bug

2018-03-28 Thread PePa
I didn't understand clearly what you were expecting until I actually ran your example. I think this shows your expectations more clearly: test a = a && { echo this line should be displayed test a = b && { echo this line should not be displayed and is not } # echo uncomment this line an

proper bash configure behavior when /dev/stdin is present, /dev/{,self/}fd are not?

2018-03-28 Thread Brian Carnes
When configuring bash on a self-hosted QNX 6.6 or QNX7 system: This is an OS that has /dev/stdin and friends, but does not have /dev/fd. When blind cross-compiling bash for QNX, one would get a guess answer of: bash_cv_dev_fd=standard bash_cv_dev_stdin=present When doing the safer self-hoste

proper bash configure behavior when /dev/stdin is present, /dev/{,self/}fd are not?

2018-03-28 Thread Brian Carnes
When configuring bash on a self-hosted QNX 6.6 or QNX7 system: This is an OS that has /dev/stdin and friends, but does not have /dev/fd. When blind cross-compiling bash for QNX, one would get a guess answer of: bash_cv_dev_fd=standard bash_cv_dev_stdin=present When doing the safer self-hoste