Re: with bash 3.2 from source: hashmarks inside backticks cause parse er
From:
Chet Ramey
Subject:
Re: with bash 3.2 from source: hashmarks inside backticks cause parse error
Date:
Fri, 24 Oct 2008 10:25:11 -0400
User-agent:
Thunderbird 2.0.0.17 (Macintosh/20080914)
Tim München wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation
> CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu'
> -DCONF_MACHTYPE='i686-redhat-linux-gnu' -DCONF_VENDOR='redhat'
> -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I.
> -I. -I./include -I./lib -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g
> -pipe -m32 -march=i386 -mtune=pentium4
> uname output: Linux grid-ui.physik.uni-wuppertal.de
> 2.6.9-67.0.4.EL_SFS2.3_0smp #1 SMP Mon Jul 21 13:57:38 CEST 2008 i686 i686
> i386 GNU/Linux
> Machine Type: i686-redhat-linux-gnu
>
> Bash Version: 3.2
> Patch Level: 0
> Release Status: release
>
> Description:
> A script containing some commands including hashmarks inside a
> backtick operator fails to run correctly. The hashmark(s) seem to be
> interpreted in a way that treats the rest of the line as comment, causing the
> closing backtick to be skipped, and finally resulting in a unexpected EOF
> parse error.
This was fixed in bash-3.2 patch 1.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/