[Home]

Summary:ASTERISK-14793: Crash in device state handling
Reporter:Andrew Parisio (parisioa)Labels:
Date Opened:2010-03-23 11:42:10Date Closed:2011-06-07 14:00:58
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I finally had it set up for a backtrace when it happened, with verbose logging to file turned on.  The system was in the middle of a reload when the crash happened.  Here is the backtrace info.  I'm not 100% sure if i'm supposed to post this here but the asterisk debugging page on voip-info said submit a ticket.  I confirmed with a user that they had dialed their phone when the crash happened, and that at that instant everybody else said their phones had died.  The dial is actually a scripted button which uses the AMI to originate the call.

(gdb) bt
#0  0x0811eb99 in handle_statechange (datap=0xac080df8) at pbx.c:3387
#1  0x0816a4f9 in tps_processing_function (data=0xb7a24ab0) at taskprocessor.c:310
#2  0x0817c8b2 in dummy_start (data=0xb7a21670) at utils.c:968
#3  0xb7c5e4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#4  0xb7d556de in clone () from /lib/i686/cmov/libc.so.6
(gdb) bt full
#0  0x0811eb99 in handle_statechange (datap=0xac080df8) at pbx.c:3387
       buf = "SIP/1655\000SIP/16551\000\000øf\035\b\016g\035\bèJ¢·\214K¢·\235\221\026\b\000\000\000\000\000\000\000\000èJ¢·\001\000\000\000\000\000\000\000ôßÆ·\bs\230·Ù´\026\b,_\035\b\201\001\000"
       parse = 0xb79872a1 "SIP/16551"
       state = 8
       cblist = (struct ast_state_cb *) 0x822e278
       cur = 0xb7987298 "SIP/1655"
       hint = (struct ast_hint *) 0x89879c8
       sc = (struct statechange *) 0xac080df8
       __PRETTY_FUNCTION__ = "handle_statechange"
#1  0x0816a4f9 in tps_processing_function (data=0xb7a24ab0) at taskprocessor.c:310
       i = (struct ast_taskprocessor *) 0xb7a24ab0
       t = (struct tps_task *) 0xac0a8330
       size = 0
       __PRETTY_FUNCTION__ = "tps_processing_function"
#2  0x0817c8b2 in dummy_start (data=0xb7a21670) at utils.c:968
       __cancel_buf = {__cancel_jmp_buf = {{__cancel_jmp_buf = {-1211703308, 0, 0, -1214745656, 619094161, 999252462}, __mask_was_saved = 0}}, __pad = {0xb7987490, 0x0,
   0x0, 0x0}}
       __cancel_routine = (void (*)(void *)) 0x8077f5d <ast_unregister_thread>
       __cancel_arg = (void *) 0xb7987b90
       not_first_call = 0
       ret = (void *) 0x0
       a = {start_routine = 0x816a2d4 <tps_processing_function>, data = 0xb7a24ab0,
 name = 0xb7a21738 "tps_processing_function started at [  451] taskprocessor.c ast_taskprocessor_get()"}
       lock_info = (struct thr_lock_info *) 0x8231910
       mutex_attr = {__size = "\001\000\000", __align = 1}
#3  0xb7c5e4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
No symbol table info available.
#4  0xb7d556de in clone () from /lib/i686/cmov/libc.so.6
No symbol table info available.
Comments:By: Andrew Parisio (parisioa) 2010-03-23 16:18:02

In the meantime would it help if i removed the subscribe context that the reception console uses to monitor the 100+ sip peers?  Anything to remove the potential for this crash would be great while we work on resolving it.

Thanks!
By: Paul Belanger (pabelanger) 2010-07-24 21:54:12

Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.6.0 and 1.6.1 branches has ended. For continued maintenance support please move to the 1.6.2 branch.

More information on this change can be found in the release announcement: http://www.asterisk.org/node/49924
By: Paul Belanger (pabelanger) 2010-08-04 11:54:44

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.

Further information can be found at http://www.asterisk.org/developers/bug-guidelines