Bug#563071: vim-nox: segfault after setpos(".", [0, 1, 0, 0])

[Thomas Arendsen Hein]

Package: vim-nox
Version: 2:7.2.284-1
Severity: normal

After calling setpos(".", [0, 1, 0, 0]) vim behaves strangely, some functions
not working, x (delete) causes a segfault

To reproduce run on a shell:

echo foo > foo; vim -u NONE -U NONE -c 'call setpos(".", [0, 1, 0, 0])' -c 'normal x' foo

I can reproduce this with vim-nox and vim (i.e. vim.basic) on two different
machines with x86 userland and -686 kernel (2.6.26-2-xen-686 on the other).

When using
setpos(".", [0, 1, 1, 0])
the problem does not occur.

On Debian etch (vim 1:7.1.314-3+lenny2) the problem does not exist.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (550, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages vim-nox depends on:
ii  libacl1                   2.2.49-1       Access control list shared library
ii  libc6                     2.10.2-2       GNU C Library: Shared libraries
ii  libgpm2                   1.20.4-3.2     General Purpose Mouse - shared lib
ii  libncurses5               5.7+20090803-2 shared libraries for terminal hand
ii  libperl5.10               5.10.1-8       shared Perl library
ii  libruby1.8                1.8.7.174-3    Libraries necessary to run Ruby 1.
ii  libselinux1               2.0.89-4       SELinux runtime shared libraries
ii  python2.5                 2.5.4-3        An interactive high-level object-o
ii  tcl8.4                    8.4.19-4       Tcl (the Tool Command Language) v8
ii  vim-common                2:7.2.284-1    Vi IMproved - Common files
ii  vim-runtime               2:7.2.284-1    Vi IMproved - Runtime files

vim-nox recommends no packages.

Versions of packages vim-nox suggests:
pn  cscope                        <none>     (no description available)
pn  vim-doc                       <none>     (no description available)

-- no debconf information