[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

`read -a': spurious ctrl char when unescaping

From: Daniel Dawson
Subject: `read -a': spurious ctrl char when unescaping
Date: Sun, 17 Sep 2006 21:36:30 -0700

Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL 
-DHAVE_CONFIG_H   -I.  -I../bash -I../bash/include -I../bash/lib   -g -O2
uname output: Linux ddawson.foo 2.6.17-ddawson #5 Sat Sep 16 12:04:46 PDT 2006 
i686 GNU/Linux
Machine Type: i486-pc-linux-gnu

Bash Version: 3.1
Patch Level: 17
Release Status: release

        `read -a' is inserting a spurious ASCII 1 whenever it encounters a
        backslash-escaped character. To be precise, it appears the backslash is
        simply replaced by this character. For instance, the string "foo\ bar"
        comes out as the sequence 66 6f 6f 01 20 62 61 72, instead of
        66 6f 6f 20 62 61 72.

        $ read -a ary
        foo\ bar\\baz\"quux
        $ echo -n ${ary[0]} | hexdump -C

reply via email to

[Prev in Thread] Current Thread [Next in Thread]