[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: compgen -W "$(ls $HOME)" -> malloc error
From: |
Ian Macdonald |
Subject: |
Re: compgen -W "$(ls $HOME)" -> malloc error |
Date: |
Mon, 6 May 2002 15:06:31 -0700 |
User-agent: |
Mutt/1.3.28i |
On Mon 06 May 2002 at 18:18:37 +0000, you 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-pc-linux-gnu'
> -DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H -D_GNU_SOURCE -I. -I.
> -I./include -I./lib -O2 -march=i386 -mcpu=i686
> uname output: Linux localhost.localdomain 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT
> 2001 i686 unknown
> Machine Type: i686-pc-linux-gnu
>
> Bash Version: 2.05a
> Patch Level: 0
> Release Status: release
>
> Description:
> I recently upgraded from 2.05 to 2.05a and noticed a large number of my
> completion functions running off with the CPU. Sending them a SIGINT
> gives something like:
>
> malloc: variables.c:1886: assertion botched
> free: underflow detected; mh_nbytes out of range
> last command: grep -i 'assertion botched' *
> Stopping myself...
>
> Repeat-By:
> compgen -W "$(ls $HOME)"
> compgen -W "$(echo -e "a\nb")"
>
> Fix:
> Not known. Sorry, I don't have time to investigate further at the
> moment.
>
> Workaround:
> Use single quotes to quote the argument to compgen -W where possible.
> eg. compgen -W '$(ls $HOME)'
compgen -W doesn't like newline characters in its arguments in bash
2.05a.
Ian
--
Ian Macdonald | Each person has the right to take the
ian@caliban.org | subway.
|
|
|