Re: bash doesn't execute SIGCHLD traps in correct context

On 2/4/14 10:33 AM, Alexandru Damian wrote: > Hello, > > I'm facing an interesting problem - Bash doesn't execute SIGCHLD traps > in the correct context. I'm using bash-4.2. That's not it. The `context' -- if you mean what I think you mean -- is correct. The SIGCHLD signal disposition needs spe

Re: Bad file descriptor with coproc and pipe

On Wed, Feb 05 2014, Chet Ramey wrote: > On 2/4/14, 2:34 AM, Michal Sojka wrote: > >> Bash Version: 4.2 >> Patch Level: 45 >> Release Status: release >> >> Description: >> The following commands fail: >> >> coproc while true; do echo $RANDOM; done >> cat <&${COPROC[0]} | ca

Re: declare -ia does not enfore integer type on initialisation

> > Description: > > declare -ia not enforced if variable is initiated using = > > Correct; bash applies the integer attribute after the variable assignment. > It has been this way since arrays were introduced (well, at least as far > back as bash-3.2; that's when I stopped looking). Perhaps docu

Segmentation fault when -x is added and variable contains nulls

# su - nobody No directory, logging in with HOME=/ $ cat /tmp/r LC_CTYPE=zh_TW.UTF-8 N=$(echo 統一|iconv -t big5 -f utf-8) sh -xc ': $N' $ sh /tmp/r /tmp/r: line 1: 4551 Segmentation fault LC_CTYPE=zh_TW.UTF-8 N=$(echo 統一|iconv -t big5 -f utf-8) sh -xc ': $N' Something about that embedded nul