After running an apt-get dist-upgrade (which upgraded perl, among other things)

I now have discovered new behavior:

With every valid TERM=<foo>, 'asterisk -r' segfaults.  The list I tried (ie. 
export TERM=<foo>; asterisk -r) is:
Eterm
ansi
cons25
cons25-debian
cygwin
dumb
hurd
linux
mach
mach-bold
mach-color
pcansi
rxvt
rxvt-basic
rxvt-unicode
screen
screen-256color
screen-256color-bce
screen-bce
screen-s
screen-w
sun
vt100
vt102
vt220
vt52
wsvt25
wsvt25m
xterm
xterm-256color
xterm-color
xterm-debian
xterm-mono
xterm-r5
xterm-r6
xterm-vt220
xterm-xfree86

It appears that TERM must be set to an invalid terminal type (ie. nothing in 
/lib/terminfo) for 'asterisk -r' to work:
export TERM=unknown
        Connected to Asterisk 1.8.7.1~dfsg-1 currently running on voip (pid = 
28745) 
        No entry for terminal type "unknown"; 
        using dumb terminal settings. 
        voip*CLI>
export TERM=something_random
        Connected to Asterisk 1.8.7.1~dfsg-1 currently running on voip (pid = 
28745)
        No entry for terminal type "something_random";
        using dumb terminal settings.
        voip*CLI>
export TERM=to_infinity_and_beyond
root@voip:~# asterisk -r
        Connected to Asterisk 1.8.7.1~dfsg-1 currently running on voip (pid = 
28745)
        No entry for terminal type "to_infinity_and_beyond";
        using dumb terminal settings.

If TERM doesn't exist, or is a valid terminal type, I get a segfault.
root@voip:~# unset TERM
root@voip:~# asterisk -r
        Connected to Asterisk 1.8.7.1~dfsg-1 currently running on voip (pid = 
28745)
        [429565.756093] asterisk[30475]: segfault at ffffffff801512c0 ip 
000000000051ed74 sp 00007fff80150980 error 4 in asterisk[400000+1a3000]
        Segmentation fault

root@voip:~# export TERM="linux"
root@voip:~# asterisk -r
        Connected to Asterisk 1.8.7.1~dfsg-1 currently running on voip (pid = 
28745)
        [429601.269320] asterisk[30481]: segfault at 27772270 ip 
000000000051ed74 sp 00007fff27771930 error 4 in asterisk[400000+1a3000]
        Segmentation fault

I hope this helps nail down the problem.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to