I had this issue with 1.2.22 and did a yum update to 1.2.23 but it still exists. I also tested that the segfault happens regardless of having "sticky" aliases or not.
Am I doing something wrong perhaps? Does anyone else have this problem or is it somehow exclusive to my system?
-------------
# cat /etc/redhat-release
CentOS release 6.5 (Final)
# uname -a
Linux fax 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
# fs_cli
freeswitch@internal> alias del nonexistantalias
Socket interrupted, bye!
# ps aux | grep freeswitch
root 775 0.0 0.0 103244 832 pts/1 S+ 10:02 0:00 grep freeswitch
# tail /var/log/messages
...
Apr 5 10:02:01 fax kernel: freeswitch[772]: segfault at 0 ip 00007f5a67279a1a sp 00007f5a61ddb498 error 4 in libc-2.12.so[7f5a671fa000+18b000]
....
# service freeswitch start
....
# fs_cli
freeswitch@internal> alias add testalias help
+OK
freeswitch@internal> alias del testalias
Socket interrupted, bye!
# tail /var/log/messages
...
Apr 5 10:06:07 fax kernel: freeswitch[834]: segfault at 0 ip 00007ffe47df8a1a sp 00007ffe1d809498 error 4 in libc-2.12.so[7ffe47d79000+18b000]
...
# service freeswitch start
....
# fs_cli
freeswitch@internal> alias del *
Socket interrupted, bye!
# tail /var/log/messages
...
Apr 5 10:08:07 fax kernel: freeswitch[969]: segfault at 0 ip 00007f5670e50a1a sp 00007f5646863498 error 4 in libc-2.12.so[7f5670dd1000+18b000]
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
Official FreeSWITCH Sites
FreeSWITCH-users mailing list