n...@s-z.org 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' -DLOCALEDIR='/usr/local/share/locale' -DPACKAGE='bash'
> -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -g -O2
> uname output: Linux dirac.s-z.org 2.6.26-1-openvz-686 #1 SMP Wed Sep 10
> 19:04:44 UTC 2008 i686 GNU/Linux
> Machine Type: i686-pc-linux-gnu
>
> Bash Version: 4.0
> Patch Level: 33
> Release Status: release
>
> Description:
> Completing a (single- or double-) quoted string ending in a single
> backslash causes an assertion failure:
> malloc: unknown:0: assertion botched
> free: start and end chunk sizes differ
> last command: complete -r
> Aborting...Aborted (core dumped)
>
> The problem appears to be that, if the string ends in a backslash,
> bash_dequote_filename copies two NULs into the result buffer, which
> only has room for one.
Thanks for the report. This has been fixed for bash-4.1.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
