Random crash : somewhere in trace showing switch_core_session_exec failing
Folks, My board randomly crashes sometimes making outgoing calls; The backtrace looks like: mymodule /lib/libc.so.6(__default_sa_restorer_v2+0x0)[0x404bc630]#012 /lib/libc.so.6(gsignal+0x40)[0x404bb2ec]#012 /lib/libc.so.6(abort+0x1b0)[0x404c0b04]#012 /lib/libc.so.6(__default_sa_restorer_v2+0x0)[0x404bc630]#012 mymodule /lib/libfreeswitch.so.1(*switch_core_session_exec*+0x56c)[0x4014385c]#012 /lib/libfreeswitch.so.1(*switch_core_session_execute_application_get_flags*+0x494)[0x40143ee8]#012 /lib/libfreeswitch.so.1(*switch_core_session_run*+0xea0)[0x40147980]#012 /lib/libfreeswitch.so.1(+0x59a7c)[0x40142a7c]#012 /lib/libfreeswitch.so.1(+0xdc8bc)[0x401c58bc]#012 /lib/libpthread.so.0(+0x5a90)[0x400cea90]#012 /lib/libc.so.6(clone+0x88)[0x40567fb8]#012 Is it really failing somewhere in switch_thread? Also, some times I see different set of traces, where *esl_recv_event()* fails? I am running freeswitch version 1.2.1 on my ARM board. -- Regards Bhavesh GS LAB (O) +91 20 4671 1256 (M) +91 86000 64681
You should get a full backtrace from gdb and make sure you have symbols in "mymodule" to see why its actually crashing, seems its somewhere in your module, and seems you have actually edited the backtrace to hide any details of your module, which would be where the useful data would be contained. On May 21, 2014, at 12:22 PM, Bhavesh Soni <bhavesh.soni@gslab.com> wrote:
Folks, My board randomly crashes sometimes making outgoing calls; The backtrace looks like:
mymodule /lib/libc.so.6(__default_sa_restorer_v2+0x0)[0x404bc630]#012 /lib/libc.so.6(gsignal+0x40)[0x404bb2ec]#012 /lib/libc.so.6(abort+0x1b0)[0x404c0b04]#012 /lib/libc.so.6(__default_sa_restorer_v2+0x0)[0x404bc630]#012 mymodule /lib/libfreeswitch.so.1(switch_core_session_exec+0x56c)[0x4014385c]#012 /lib/libfreeswitch.so.1(switch_core_session_execute_application_get_flags+0x494)[0x40143ee8]#012 /lib/libfreeswitch.so.1(switch_core_session_run+0xea0)[0x40147980]#012 /lib/libfreeswitch.so.1(+0x59a7c)[0x40142a7c]#012 /lib/libfreeswitch.so.1(+0xdc8bc)[0x401c58bc]#012 /lib/libpthread.so.0(+0x5a90)[0x400cea90]#012 /lib/libc.so.6(clone+0x88)[0x40567fb8]#012
Is it really failing somewhere in switch_thread? Also, some times I see different set of traces, where esl_recv_event() fails?
I am running freeswitch version 1.2.1 on my ARM board.
-- Regards Bhavesh GS LAB (O) +91 20 4671 1256 (M) +91 86000 64681 _________________________________________________________________________ Professional FreeSWITCH Consulting Services: 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 http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Yes specifically again, in mymodule.so, I have certain pointers to offset addresses only. But, per my discussions with my fellow teammates the underlying switch_core* calls are thought to be culprits. I am parallel looking to mymodule.so calls as well; Again on the other hand, do you think because of *esl_recv_event()* failure and third thread call to ESL socket and can cause crash? Regards Bhavesh GS LAB (O) +91 20 4671 1256 (M) +91 86000 64681 On 21-05-2014 18:01, Michael Jerris wrote:
You should get a full backtrace from gdb and make sure you have symbols in "mymodule" to see why its actually crashing, seems its somewhere in your module, and seems you have actually edited the backtrace to hide any details of your module, which would be where the useful data would be contained.
On May 21, 2014, at 12:22 PM, Bhavesh Soni <bhavesh.soni@gslab.com <mailto:bhavesh.soni@gslab.com>> wrote:
Folks, My board randomly crashes sometimes making outgoing calls; The backtrace looks like:
mymodule /lib/libc.so.6(__default_sa_restorer_v2+0x0)[0x404bc630]#012 /lib/libc.so.6(gsignal+0x40)[0x404bb2ec]#012 /lib/libc.so.6(abort+0x1b0)[0x404c0b04]#012 /lib/libc.so.6(__default_sa_restorer_v2+0x0)[0x404bc630]#012 mymodule /lib/libfreeswitch.so.1(*switch_core_session_exec*+0x56c)[0x4014385c]#012 /lib/libfreeswitch.so.1(*switch_core_session_execute_application_get_flags*+0x494)[0x40143ee8]#012 /lib/libfreeswitch.so.1(*switch_core_session_run*+0xea0)[0x40147980]#012 /lib/libfreeswitch.so.1(+0x59a7c)[0x40142a7c]#012 /lib/libfreeswitch.so.1(+0xdc8bc)[0x401c58bc]#012 /lib/libpthread.so.0(+0x5a90)[0x400cea90]#012 /lib/libc.so.6(clone+0x88)[0x40567fb8]#012
Is it really failing somewhere in switch_thread? Also, some times I see different set of traces, where *esl_recv_event()* fails?
I am running freeswitch version 1.2.1 on my ARM board.
-- Regards Bhavesh GS LAB (O) +91 20 4671 1256 (M) +91 86000 64681 _________________________________________________________________________ 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 http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: 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 http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
So switch_core_session_exec is what is calling your module, which is then crashing, and you think the problem is in switch_core_session_exec? On May 21, 2014, at 12:44 PM, Bhavesh Soni <bhavesh.soni@gslab.com> wrote:
Yes specifically again, in mymodule.so, I have certain pointers to offset addresses only. But, per my discussions with my fellow teammates the underlying switch_core* calls are thought to be culprits. I am parallel looking to mymodule.so calls as well;
Again on the other hand, do you think because of esl_recv_event() failure and third thread call to ESL socket and can cause crash? Regards Bhavesh GS LAB (O) +91 20 4671 1256 (M) +91 86000 64681 On 21-05-2014 18:01, Michael Jerris wrote:
You should get a full backtrace from gdb and make sure you have symbols in "mymodule" to see why its actually crashing, seems its somewhere in your module, and seems you have actually edited the backtrace to hide any details of your module, which would be where the useful data would be contained.
On May 21, 2014, at 12:22 PM, Bhavesh Soni <bhavesh.soni@gslab.com> wrote:
Folks, My board randomly crashes sometimes making outgoing calls; The backtrace looks like:
mymodule /lib/libc.so.6(__default_sa_restorer_v2+0x0)[0x404bc630]#012 /lib/libc.so.6(gsignal+0x40)[0x404bb2ec]#012 /lib/libc.so.6(abort+0x1b0)[0x404c0b04]#012 /lib/libc.so.6(__default_sa_restorer_v2+0x0)[0x404bc630]#012 mymodule /lib/libfreeswitch.so.1(switch_core_session_exec+0x56c)[0x4014385c]#012 /lib/libfreeswitch.so.1(switch_core_session_execute_application_get_flags+0x494)[0x40143ee8]#012 /lib/libfreeswitch.so.1(switch_core_session_run+0xea0)[0x40147980]#012 /lib/libfreeswitch.so.1(+0x59a7c)[0x40142a7c]#012 /lib/libfreeswitch.so.1(+0xdc8bc)[0x401c58bc]#012 /lib/libpthread.so.0(+0x5a90)[0x400cea90]#012 /lib/libc.so.6(clone+0x88)[0x40567fb8]#012
Is it really failing somewhere in switch_thread? Also, some times I see different set of traces, where esl_recv_event() fails?
I am running freeswitch version 1.2.1 on my ARM board.
-- Regards Bhavesh GS LAB (O) +91 20 4671 1256 (M) +91 86000 64681 _________________________________________________________________________ Professional FreeSWITCH Consulting Services: 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 http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: 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 http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: 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 http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Probably if you didn't redact out the mymodule it would point out where your crash is. Stack traces are upside down so the top of the stack is usually where the problem is. If mymodule is top secret you may have to pursue commerical support. On Wed, May 21, 2014 at 8:07 AM, Michael Jerris <mike@jerris.com> wrote:
So switch_core_session_exec is what is calling your module, which is then crashing, and you think the problem is in switch_core_session_exec?
On May 21, 2014, at 12:44 PM, Bhavesh Soni <bhavesh.soni@gslab.com> wrote:
Yes specifically again, in mymodule.so, I have certain pointers to offset addresses only. But, per my discussions with my fellow teammates the underlying switch_core* calls are thought to be culprits. I am parallel looking to mymodule.so calls as well;
Again on the other hand, do you think because of *esl_recv_event()*failure and third thread call to ESL socket and can cause crash?
Regards Bhavesh GS LAB (O) +91 20 4671 1256 (M) +91 86000 64681
On 21-05-2014 18:01, Michael Jerris wrote:
You should get a full backtrace from gdb and make sure you have symbols in "mymodule" to see why its actually crashing, seems its somewhere in your module, and seems you have actually edited the backtrace to hide any details of your module, which would be where the useful data would be contained.
On May 21, 2014, at 12:22 PM, Bhavesh Soni <bhavesh.soni@gslab.com> wrote:
Folks, My board randomly crashes sometimes making outgoing calls; The backtrace looks like:
mymodule /lib/libc.so.6(__default_sa_restorer_v2+0x0)[0x404bc630]#012 /lib/libc.so.6(gsignal+0x40)[0x404bb2ec]#012 /lib/libc.so.6(abort+0x1b0)[0x404c0b04]#012 /lib/libc.so.6(__default_sa_restorer_v2+0x0)[0x404bc630]#012 mymodule /lib/libfreeswitch.so.1(*switch_core_session_exec*+0x56c)[0x4014385c]#012 /lib/libfreeswitch.so.1( *switch_core_session_execute_application_get_flags*+0x494)[0x40143ee8]#012 /lib/libfreeswitch.so.1(*switch_core_session_run*+0xea0)[0x40147980]#012 /lib/libfreeswitch.so.1(+0x59a7c)[0x40142a7c]#012 /lib/libfreeswitch.so.1(+0xdc8bc)[0x401c58bc]#012 /lib/libpthread.so.0(+0x5a90)[0x400cea90]#012 /lib/libc.so.6(clone+0x88)[0x40567fb8]#012
Is it really failing somewhere in switch_thread? Also, some times I see different set of traces, where *esl_recv_event()*fails?
I am running freeswitch version 1.2.1 on my ARM board.
-- Regards Bhavesh GS LAB (O) +91 20 4671 1256 (M) +91 86000 64681
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: 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 http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services:consulting@freeswitch.orghttp://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Serverhttp://www.cudatel.com
Official FreeSWITCH Siteshttp://www.freeswitch.orghttp://wiki.freeswitch.orghttp://www.cluecon.com
FreeSWITCH-users mailing listFreeSWITCH-users@lists.freeswitch.orghttp://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-usershttp://www.frees...
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: 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 http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: 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 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 #freeswitch ☞ *http://freeswitch.org/g+ <http://freeswitch.org/g+>* ClueCon Weekly Development Call ☎ sip:888@conference.freeswitch.org ☎ +19193869900
participants (3)
-
Anthony Minessale
-
Bhavesh Soni
-
Michael Jerris