[Home]

Summary:ASTERISK-16326: Crash in sip_alloc
Reporter:Kristijan Vrban (vrban)Labels:
Date Opened:2010-07-07 08:47:20Date Closed:2011-06-07 14:00:27
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) bt_full.txt
Description:i had a crash in sip_alloc from app_queue to a call to a SIP Agent. See attached gdb output.

****** ADDITIONAL INFORMATION ******

Last full log:
Jul  7 14:07:52 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Executing [*770002-K2300@main-functions:3] ExecIf("SIP/BTNGN3-00020955", "1|Queue|K2300-0002||||720") in new stack
Jul  7 14:07:52 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Started music on hold, class 'Q0218', on SIP/BTNGN3-00020955
Jul  7 14:07:52 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- SIP/K230005323-00020958 is circuit-busy
Jul  7 14:07:52 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Nobody picked up in 0 ms
Jul  7 14:07:58 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- SIP/K230005323-00020959 is circuit-busy
Jul  7 14:07:58 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Nobody picked up in 1000 ms
Jul  7 14:08:03 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- SIP/K230005323-0002095a is circuit-busy
Jul  7 14:08:03 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Nobody picked up in 0 ms
Jul  7 14:08:09 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- SIP/K230005323-0002095b is circuit-busy
Jul  7 14:08:09 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Nobody picked up in 0 ms
Jul  7 14:08:14 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- SIP/K230005323-0002095c is circuit-busy
Jul  7 14:08:14 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Nobody picked up in 0 ms
Jul  7 14:08:20 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- SIP/K230005323-00020966 is circuit-busy
Jul  7 14:08:20 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Nobody picked up in 0 ms
Jul  7 14:08:25 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- SIP/K230005323-00020968 is circuit-busy
Jul  7 14:08:25 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Nobody picked up in 0 ms
Jul  7 14:08:31 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- SIP/K230005323-0002096c is circuit-busy
Jul  7 14:08:31 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Nobody picked up in 1000 ms
Jul  7 14:08:36 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- SIP/K230005323-0002096f is circuit-busy
Jul  7 14:08:36 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Nobody picked up in 0 ms
Jul  7 14:08:42 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- SIP/K230005323-00020970 is circuit-busy
Jul  7 14:08:42 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Nobody picked up in 0 ms
Jul  7 14:08:48 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- SIP/K230005323-00020973 is circuit-busy
Jul  7 14:08:48 172.22.2.19 asterisk[18932]: VERBOSE[6420]:     -- Nobody picked up in 0 ms

<crash>
Comments:By: Paul Belanger (pabelanger) 2010-07-07 09:01:28

Your backtrace is optimized (see below).
---
Thank you for your bug report. In order to move your issue forward, we require a backtrace from the core file produced after the crash. Please see the doc/backtrace.txt file in your Asterisk source directory.

Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then:

make install

after enabling, reproduce the crash, and then execute the instructions in doc/backtrace.txt.

When complete, attach that file to this issue report. Thanks!
By: David Woolley (davidw) 2010-07-07 09:14:55

Also, this is a memory management problem, so you will probably need to follow the procedure in doc/valgrind.txt.
By: Leif Madsen (lmadsen) 2010-07-07 09:40:22

Marking as Feedback while we await unoptimized backtrace and valgrind results.
By: Kristijan Vrban (vrban) 2010-07-08 03:11:09

i would like to offer a unoptimized backtrace, but this crash is not yet reproducible.
By: Paul Belanger (pabelanger) 2010-07-08 07:55:55

Suspending for now.  Once you can reproduce the issue, simply reopen the issue.

---
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