Re: nameref subscript assignment with unset target var

2016-05-18 Thread Chet Ramey
On 5/17/16 4:40 PM, Grisha Levit wrote: > Multiple variables with the same name are created at the same scope when > doing assignments to subscripts of nameref variables that point to > variables that are unset. > > |$ unset var; declare -n ref=var; ref[0]=foo $ declare -p ref declare -a > ref=([0

Re: export/readonly unset value of target variable if passed an array reference

2016-05-18 Thread Chet Ramey
On 5/17/16 8:33 PM, Grisha Levit wrote: > |$ var=foo; declare -n ref=var[0] $ readonly ref $ declare -p var declare > -ar var | > > works even with readonly variables: Thanks for the report. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita

Re: segfault on stack blowup with ridiculous && chains

2016-05-18 Thread Chet Ramey
On 5/18/16 10:02 AM, Sarah Brofeldt wrote: > I'm not sure whether this is actually acceptable behaviour, but a > ridiculously long && chain blows up bash: Bash will obediently attempt to run what you tell it to until it runs out of resources. -- ``The lyf so short, the craft so long to lerne.''

segfault on stack blowup with ridiculous && chains

2016-05-18 Thread Sarah Brofeldt
I'm not sure whether this is actually acceptable behaviour, but a ridiculously long && chain blows up bash: echo -n "" && echo -n "" && (... repeated 100.000 times) echo -n "" causes a segfault with ulimit -s 8192 in bash 4.3.42(1)-release and 4.4.0(1)-rc2