zsh segfaults on $(( [#2] 0xDEADBEEF ))

[Andre Pang <ozone@algorithm.com.au>]

using zsh as a calculator:

    18:00 ~% zsh
    18:00 ~% echo $(( [#16] 0xDEADBEEF ))
    16#DEADBEEF
    18:00 ~% echo $(( [#8] 0xDEADBEEF ))
    8#33653337357
    18:00 ~% echo $(( [#4] 0xDEADBEEF ))
    4#3132223123323233
    18:00 ~% echo $(( [#3] 0xDEADBEEF ))
    3#100122100210211112102
    18:00 ~% echo $(( [#2] 0xDEADBEEF ))
    zsh: 6139 segmentation fault  zsh
    18:00 ~% 

after a few more seconds of playing around (i am now friends
with Esc A):

    18:02 ~% echo $(( [#2] 0x1FFFFF ))
    2#111111111111111111111
    18:02 ~% echo $(( [#2] 0x200000 ))
    zsh: 6192 segmentation fault  zsh

and

    18:07 ~% echo $(( [#3] 0x26F7C528F ))
    3#222222222222222221200
    18:07 ~% echo $(( [#3] 0x26F7C5300 ))
    zsh: 6370 segmentation fault  zsh

this has happened to two machines i've tried it on:

    18:10 wagner:~% uname -a
    Linux wagner 2.4.3 #2 SMP Sat Apr 7 04:28:16 EST 2001 i686 unknown
    18:10 wagner:~% echo $ZSH_VERSION
    3.1.9-dev-6

    18:07 ~% uname -a 
    Linux exodus 2.4.2-exodus #31 Fri Mar 16 09:22:38 EST 2001 i686 unknown
    18:08 ~% echo $ZSH_VERSION
    4.0.1-debian0420

wow.  after >1 year of not finding a single bug in zsh, i
suddenly find two major-ish ones in the same day :)

please cc replies to me (or zsh-users) -- i'm not on zsh-workers.


-- 
#ozone/algorithm <ozone@algorithm.com.au>          - trust.in.love.to.save