Package: libtinfo5
Version: 5.9+20130504-1
Severity: normal
If you run a program that uses tgetent() -- at least bash and gdb, with
TERM=KBtin, it will segfault on startup. Its terminfo definition can be
found in package "kbtin", or by tic-ing:
kbtin|KBtin|KBtin's spawned pseudo-terminal,
am, bce, xenl, eo, hc, it#8, colors#8, bel=^G, el1=\e[K,
blink=\e[5m, bold=\e[1m, dim=\e[2m, sitm=\e[3m, smul=\e[4m,
sgr0=\e[m, ritm=\e[24m, rmul=\e[24m, setab=\e[4%p1%dm,
setaf=\e[3%p1%dm, ind=^J, nel=^J, dl1=\e[2K, smso=\e[0;1;47m,
rmso=\e[0m, sgr=\E[0%?%p1%p6%|%t;1%;%?%p2%|%t;4%;%?%p4%|%t;5%;
%?%p5%|%t;2%;m, lm#0,
This terminal is pretty limited, basically hardcopy with colors (enough for
both bash and gdb), but as far as I'm aware, these settings are valid. And
in any case, a core library shouldn't crash on any external input, be it
valid or not.
This segfault happens for me on at least amd64, armhf and 386, on current
unstable but not on wheezy (nor did it a decade ago when this definition was
written).
I haven't excluded the possibility something else it to blame, but debugging
through tinfo's code is a pain: it's layers upon layers of macros. At
least, at the time of segfault, the values in cur_term are bogus.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (150, 'experimental')
Architecture: armhf (armv7l)
Kernel: Linux 3.0.68 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libtinfo5 depends on:
ii libc6 2.17-4
ii multiarch-support 2.17-4
libtinfo5 recommends no packages.
libtinfo5 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
