Bug#649431: segmentation fault in asterisk -r

[Troy Telford]

With asterisk 1:1.8.7.1~dfsg-1, I am also reproducing this error; my core dump shows:

root at 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  0x000000000051ed74 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.groups at gmail.com