So, I am still curious about my question though. Do I need to test bugs against the master branch or is the 1.2-stable branch okay? Also, the segfault problem with the "complete" command is because in the code it doesn't check for a 2nd variable on "complete add" but tries to use a 2nd variable (of course, since it needs one). So if you type "complete add" and press enter it will segfault. I'll make a JIRA ticket but I wanted to know the rules first. On Saturday, April 5, 2014 01:43 PM CDT, Sean Devoy <sdevoy@bizfocused.com> wrote:
LOL. OK Anthony now you are just showing off!
From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Saturday, April 05, 2014 12:09 PM To: FreeSWITCH Users Help Subject: Re: [Freeswitch-users] FreeSWITCH 1.2.22/1.2.23 segfault when using console command alias del
Too late, fixed in both trees.
On Sat, Apr 5, 2014 at 11:01 AM, <bruce@sqls.net<mailto:bruce@sqls.net>> wrote:
Thanks Brian, sorry about posting all the details here.
In that wiki page it says to first test using the latest git. So I would need to test the error on the v1.5 code from git first before making a ticket? Or just the latest from the 1.2 stable?
Side note, I also found a segfault error with the complete command and am able to see in the code what causes it (i think) but I haven't figured out the alias error yet.
------ Original Message ------ From: "Brian West" <brian@freeswitch.org<mailto:brian@freeswitch.org>> To: "FreeSWITCH Users Help" <freeswitch-users@lists.freeswitch.org<mailto:freeswitch-users@lists.freeswitch.org>> Sent: 4/5/2014 10:19:09 AM Subject: Re: [Freeswitch-users] FreeSWITCH 1.2.22/1.2.23 segfault when using console command alias del
https://wiki.freeswitch.org/wiki/Reporting_Bugs
Please get a backtrace, and open a JIRA -- Brian West brian@freeswitch.org<mailto:brian@freeswitch.org> FreeSWITCH Solutions, LLC PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com<http://www.freeswitchbook.com/> http://www.freeswitchcookbook.com<http://www.freeswitchcookbook.com/>
T: +1.918.420.9001<tel:%2B1.918.420.9001> | F: +1.918.420.9002<tel:%2B1.918.420.9002> | M: +1.918.424.WEST iNUM: +883 5100 1420 9001<tel:%2B883%205100%201420%209001> ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED)
On Apr 5, 2014, at 10:14 AM, bruce@sqls.net<mailto:bruce@sqls.net> wrote:
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<http://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<http://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<http://libc-2.12.so>[7f5670dd1000+18b000]
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com<http://www.freeswitchsolutions.com/>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com<http://www.cudatel.com/>
Official FreeSWITCH Sites http://www.freeswitch.org<http://www.freeswitch.org/> http://wiki.freeswitch.org<http://wiki.freeswitch.org/> http://www.cluecon.com<http://www.cluecon.com/>
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org<http://www.freeswitch.org/>
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II ♬ @anthmfs ♬ @FreeSWITCH ♬
☞ http://freeswitch.org/ ☞ http://cluecon.com/ ☞ http://twitter.com/FreeSWITCH ☞ irc.freenode.net<http://irc.freenode.net> #freeswitch ☞ http://freeswitch.org/g+ ClueCon Weekly Development Call ☎ sip:888@conference.freeswitch.org<mailto:sip%3A888@conference.freeswitch.org> ☎ +19193869900