Re: Possible bug in bash error reporting

[Chet Ramey]

Jan Schampera wrote:
> 
> Configuration Information [Automatically generated, do not change]:
>  Machine: i586
>  OS: linux-gnu
>  Compiler: gcc
>  Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i586'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-mandrake-linux-gnu'
> -DCONF_VENDOR='mandrake' -DLOCALEDIR='/usr/share/locale'
> -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H  -I.  -I.. -I../include
> -I../lib  -D_GNU_SOURCE  -O2 -fomit-frame-pointer -pipe -march=i586
> -mtune=pentiumpro  uname output: Linux mainserver 2.6.11.11 #1 Sat Jun 4
> 00:31:34 CEST 2005 i686 AMD Sempron(TM) 2800+ unknown GNU/Linux Machine
> Type: i586-mandrake-linux-gnu
> 
>  Bash Version: 3.0
>  Patch Level: 13
>  Release Status: release
> 
>  Description:
>       Say, you have a file, A.sh, and source another file, B.sh, all
> errors in B.sh are reported with the line number of B.sh. BUT: it seems
> that only internal (parser? interpreter?) errors are reported mentioning
> B.sh. Errors generated by builtins and errors during the execution of a
> program just come up with only the linenumber. Also present in 2.x
> versions.

I can reproduce this in bash-2.05b, but not in bash-3.x.  I suspect
you're running some version of bash-2.05 as /bin/sh and seeing the
error as a result.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
                                                Live...Laugh...Love
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/