[asterisk-bugs] [JIRA] (ASTERISK-21806) Segfault in CHAN_SIP - in _int_malloc while in __ast_cc_config_params_init

Thu May 30 15:59:03 CDT 2013

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206871#comment-206871 ] 

Rusty Newton edited comment on ASTERISK-21806 at 5/30/13 3:58 PM:
------------------------------------------------------------------

this system continues to dump core every day or two  with int_malloc as the culprit thread..  this is with the debug_threads and malloc_debug  turned off...  better_backtraces and dont_optimize are still enabled. 
the brief backtrace shows the following:

{noformat}
(gdb) bt
#0  0xb741f8f2 in _int_malloc () from /lib/libc.so.6
#1  0xb7422070 in malloc () from /lib/libc.so.6
#2  0x0818c814 in _ast_malloc (len=192, file=0x8257854 "ccss.c", lineno=568, func=0x825a81d "__ast_cc_config_params_init")
    at /usr/src/certified-asterisk-1.8.15-cert2/include/asterisk/utils.h:471
#3  0x08092cfa in __ast_cc_config_params_init (file=0xb65432f4 "chan_sip.c", line=7823, function=0xb655acc9 "sip_alloc") at ccss.c:568
#4  0xb64c796f in sip_alloc (
    callid=0x877cf6c "3671154305879-0638726692926-09081817718674-011791077788251-014501739868498-01721655633282-019921250221658-022631305372974-025341427188938-028051276386395-03075215139569-03346626186307-03617159340434-0"..., addr=0xb63cbc3c, useglobal_nat=1, intended_method=10,
    req=0xb63cbcc0) at chan_sip.c:7823
#5  0xb64c9a2c in find_call (req=0xb63cbcc0, addr=0xb63cbc3c, intended_method=10) at chan_sip.c:8354
#6  0xb651bd9d in handle_request_do (req=0xb63cbcc0, addr=0xb63cbc3c) at chan_sip.c:26078
#7  0xb651bb87 in sipsock_read (id=0x85f1580, fd=10, events=1, ignore=0x0) at chan_sip.c:26034
#8  0x0810e1f0 in ast_io_wait (ioc=0x85dca50, howlong=1000) at io.c:292
#9  0xb651d928 in do_monitor (data=0x0) at chan_sip.c:26586
#10 0x0818dc0f in dummy_start (data=0x85e9af0) at utils.c:1071
#11 0xb7208e99 in start_thread () from /lib/libpthread.so.0
#12 0xb7487d2e in clone () from /lib/libc.so.6
(gdb)
{noformat}

      was (Author: cadillackid):
    this system continues to dump core every day or two  with int_malloc as the culprit thread..  this is with the debug_threads and malloc_debug  turned off...  better_backtraces and dont_optimize are still enabled. 
the brief backtrace shows the following:
(gdb) bt
#0  0xb741f8f2 in _int_malloc () from /lib/libc.so.6
#1  0xb7422070 in malloc () from /lib/libc.so.6
#2  0x0818c814 in _ast_malloc (len=192, file=0x8257854 "ccss.c", lineno=568, func=0x825a81d "__ast_cc_config_params_init")
    at /usr/src/certified-asterisk-1.8.15-cert2/include/asterisk/utils.h:471
#3  0x08092cfa in __ast_cc_config_params_init (file=0xb65432f4 "chan_sip.c", line=7823, function=0xb655acc9 "sip_alloc") at ccss.c:568
#4  0xb64c796f in sip_alloc (
    callid=0x877cf6c "3671154305879-0638726692926-09081817718674-011791077788251-014501739868498-01721655633282-019921250221658-022631305372974-025341427188938-028051276386395-03075215139569-03346626186307-03617159340434-0"..., addr=0xb63cbc3c, useglobal_nat=1, intended_method=10,
    req=0xb63cbcc0) at chan_sip.c:7823
#5  0xb64c9a2c in find_call (req=0xb63cbcc0, addr=0xb63cbc3c, intended_method=10) at chan_sip.c:8354
#6  0xb651bd9d in handle_request_do (req=0xb63cbcc0, addr=0xb63cbc3c) at chan_sip.c:26078
#7  0xb651bb87 in sipsock_read (id=0x85f1580, fd=10, events=1, ignore=0x0) at chan_sip.c:26034
#8  0x0810e1f0 in ast_io_wait (ioc=0x85dca50, howlong=1000) at io.c:292
#9  0xb651d928 in do_monitor (data=0x0) at chan_sip.c:26586
#10 0x0818dc0f in dummy_start (data=0x85e9af0) at utils.c:1071
#11 0xb7208e99 in start_thread () from /lib/libpthread.so.0
#12 0xb7487d2e in clone () from /lib/libc.so.6
(gdb)

> Segfault in CHAN_SIP - in _int_malloc while in __ast_cc_config_params_init
> --------------------------------------------------------------------------
>
>                 Key: ASTERISK-21806
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21806
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.15.0
>         Environment: CPU: Atom D525, RAM 4GB, Fedora Linux, Kernel 2.6.43.8-1.i686
> 2 Aastra endpoints, 1 Polycom IP-650, 1 96 port SIP to analog gateway
> Asterisk 1.8.15-cert2
>            Reporter: Christopher
>            Assignee: Christopher
>         Attachments: core-dump-maxx-052213.txt, valgrind-052213-1530.txt, valgrind-0523-1545-no-malloc.txt, valgrind-good-052213-1930.txt
>
>
> Segfault occurs whether system is idle or is in-use. it will crash within a day or two even if 0 calls are made on it.  running under safe_asterisk, results in multiple crashes within a few minutes until eventually system ends up in a MUTEX lock. over 3 gigs of RAM available and plenty of disk space at time of first crash. Possibly related to the 96 port gateway producing 96 SIP registrations all at once?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira