> Machine Type: i686-pc-linux-gnu
>
> Bash Version: 4.0
> Patch Level: 0
> Release Status: release
>
> Description:
> When attempting tab completion, the following error occcurs:
> malloc: /Users/chet/src/bash/src/parse.y:5561: assertion botched
> free: called wi
On Sun, Mar 15, 2009 at 07:21:06AM -, t...@accesslab.com wrote:
> This command sequence concatenates a text string with a $'\NNN' string
> producing an error:
> shopt -s extglob; x="hello"$'\179'; echo "${x//+([^[:print:]])/?}"
>
> EXPECTED RESULT IS -> hello?
>
>
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-pc-linux-gnu'
-DCONF_VENDOR='pc'
-DLOCALEDIR='/fast-storage/users/l/lil_cain/
I just sent a bug report with the above description; please ignore.. I'm
an idiot. There is no error actually my math was bad.
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: i686-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/loc
Stephane CHAZELAS wrote:
> 2009-03-10, 15:43(-04), Chet Ramey:
>>> What are the valid charactes for the IFS variable? In particular, is '\0' a
>>> valid one?
>> Technically, yes, but in practice it's not useful. There are too many things
>> represented as C strings to make NUL work right.
> [..