commands do not ignore TSTP if TSTP ignored already

2014-10-15 Thread idallen
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-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA

Re: Fwd: Testing for Shellshock...

2014-10-15 Thread Eduardo A . Bustamante López
> I believe it would be interesting to measure the combinatorial coverage of > the fuzz tests. You already asked this... why didn't you follow up in the thread that you started? > [...] So we would be able to say what percentage of 2-way, > 3-way, etc. combinations are covered, which would be use

Re: Weirdness in associative array assignements

2014-10-15 Thread Chet Ramey
On 10/15/14, 4:55 AM, dnade@orange.com wrote: > Hello dear bash-bug mailing-list! > > I am puzzled by bash behavior with array assignments. > > It seems there is a behavior change introduced in bash 4.3 in array > assignments. An array can actually reference itself in its own dec

Fwd: Testing for Shellshock...

2014-10-15 Thread Rick Karcich
Inasmuch as, there apparently is now a fuzz test script(courtesy of Michal Zalewski, < http://lcamtuf.blogspot.ie/2014/10/bash-bug-how-we-finally-cracked.html > that identifies the bash bug... I believe it would be interesting to measure the combinatorial coverage of the fuzz tests. So we would

Re: Issue with Bash-4.3 Official Patch 27

2014-10-15 Thread Eric Blake
On 10/15/2014 11:49 AM, lorenz.bucher@rohde-schwarz.com wrote: > Yes, you got it. I just gave an example to reproduce that Bug. In my case > I didn't find the save script/binary yet. > I use unset -f function as workaround. > > But anyway. > In my opinion I should trust a shell not violatin

Re: Issue with Bash-4.3 Official Patch 27

2014-10-15 Thread Lorenz . Bucher . ext
Yes, you got it. I just gave an example to reproduce that Bug. In my case I didn't find the save script/binary yet. I use unset -f function as workaround. But anyway. In my opinion I should trust a shell not violating their own rules and be able to import their own variables. So the % characte

Re: Issue with Bash-4.3 Official Patch 27

2014-10-15 Thread Steve Simmons
On Oct 15, 2014, at 9:38 AM, lorenz.bucher@rohde-schwarz.com wrote: > Hello, > in refer to > http://lists.gnu.org/archive/html/bug-bash/2014-09/msg00278.html variables > with suffix "%%" can't be set/exported. > This makes problems restoring environments which where saved by external > prog

Re: Issue with Bash-4.3 Official Patch 27

2014-10-15 Thread Greg Wooledge
On Wed, Oct 15, 2014 at 08:50:25AM -0700, Eduardo A. Bustamante López wrote: > On Wed, Oct 15, 2014 at 03:38:01PM +0200, lorenz.bucher@rohde-schwarz.com > wrote: > > variables with suffix "%%" can't be set/exported. > > This makes problems restoring environments which where saved by external

Re: Issue with Bash-4.3 Official Patch 27

2014-10-15 Thread Eduardo A . Bustamante López
On Wed, Oct 15, 2014 at 03:38:01PM +0200, lorenz.bucher@rohde-schwarz.com wrote: > Hello, > in refer to > http://lists.gnu.org/archive/html/bug-bash/2014-09/msg00278.html variables > with suffix "%%" can't be set/exported. > This makes problems restoring environments which where saved by ext

Issue with Bash-4.3 Official Patch 27

2014-10-15 Thread Lorenz . Bucher . ext
Hello, in refer to http://lists.gnu.org/archive/html/bug-bash/2014-09/msg00278.html variables with suffix "%%" can't be set/exported. This makes problems restoring environments which where saved by external programs like printenv (see example below) I saw this issue on Ubuntu 12.04 with bash ve

Weirdness in associative array assignements

2014-10-15 Thread dnade.ext
Hello dear bash-bug mailing-list! I am puzzled by bash behavior with array assignments. It seems there is a behavior change introduced in bash 4.3 in array assignments. An array can actually reference itself in its own declaration. $ declare -A foo=([bar]=1st) ; foo=([bar]=2nd [qwer