Bug#649431: segmentation fault in asterisk -r
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 801512c0 ip 0051ed74 sp 7fff80150980 error 4 in asterisk[40+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 0051ed74 sp 7fff27771930 error 4 in asterisk[40+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
Bug#649431: segmentation fault in asterisk -r
With asterisk 1:1.8.7.1~dfsg-1, I am also reproducing this error; my core dump shows: root@voip:# gdb `which asterisk` core GNU gdb (GDB) 7.3-debian Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/sbin/asterisk...Reading symbols from /usr/lib/debug/usr/sbin/asterisk...done. done. [New LWP 21268] [New LWP 21269] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Core was generated by `rasterisk g -r'. Program terminated with signal 11, Segmentation fault. #0 0x0051ed74 in term_alloc (el=0x2203780, t=0x5770c0, cap=0x178552e0 Address 0x178552e0 out of bounds) at term.c:398 398 term.c: No such file or directory. in term.c (gdb) As far as terminal information, I've reproduced the problem with the following: - Serial TTY (using GNU screen as the terminal emulator) - ssh session from KDE (Konsole; TERM=xterm) - Linux Console (ie. no X11; TERM=linux) - SSH from OS X Terminal (TERM=xterm-256color) - Xen serial console (I've also created an entirely clean debian 'sid' virtual machine (using xen-tools), installed asterisk, and was able to reproduce the error) And, as is the case with Vincent Smeets, the problem started when I installed Asterisk 1.8.7.1~dfsg-1. However, unlike Vincent, unsetting the TERM environment variable does NOT make the problem go away; I still get a segmentation fault with exit status 139, every time, from every terminal (local and remote) that I've attempted to use. -- Troy Telford -- Troy Telford ttelford.gro...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
