Package: nickle
Version: 2.83-1
Severity: normal
Some literals or initializers for multidimensional arrays cause
segmentation fault instead of reporting an array dimension mismatch.
Consider these:
; nickle -e '([*,*]){1}'
segmentation violation
; nickle -e 'int[*,*] x = {1}'
segmentation violation
; nickle -e 'int[] x = {{1},2}'
segmentation violation
The following gives the expected result, however:
; nickle -e 'int[] x = {1,{2}}'
-> int[] x = { 1, { 2 } };
int[] x = {1,{2}}
:1: Array dimension mismatch 1 != 2
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (700, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8),
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages nickle depends on:
ii libc6 2.27-6
ii libncurses6 6.1+20181013-1
ii libreadline7 7.0-5
ii libtinfo6 6.1+20181013-1
nickle recommends no packages.
nickle suggests no packages.
-- no debconf information
