|Summary:||ASTERISK-11948: Crash in chan_iax2|
|Date Opened:||2008-04-30 13:29:43||Date Closed:||2011-06-07 14:00:47|
|Environment:||Attachments:||( 0) crash-thread.txt|
( 1) iax_thread.txt
( 2) iax-crash.txt
|Description:||We just experienced a crash that appears to be IAX related. Backtrace attached.|
|Comments:||By: Jason Parker (jparker) 2008-04-30 14:59:56|
We're going to need some information about when this crash occurred. From the backtrace you've provided, the crash happened in a malloc call, which (under normal circumstances) is not possible. In the case of lack of free memory, it should return NULL.
Is this a one-time crash? Is this an unoptimized build?
By: callguy (callguy) 2008-04-30 15:23:48
qwell: this was a one-time crash.
the build is unoptimized, and i have the core file and can get whatever you need. i realize that my description was a little thin at best, but we couldn't find any correlation between activity on the server and this happening. in fact - there weren't any actual IAX calls going on on this machine when the crash occurred.
the only thing we could fine at all was this on load:
[Apr 30 13:54:04] WARNING chan_iax2.c: Unable to open IAX timing interface: No such file or directory
but i'm not sure if that would be related tot he crash or not. Just let me know what we can do to help troubleshoot.
By: Jason Parker (jparker) 2008-04-30 15:42:34
What CFLAGS do you have enabled in menuselect?
Can you attach a thread apply all bt full?
By: callguy (callguy) 2008-04-30 15:46:34
We have DONT_OPTIMIZE and DEBUG_THREADS.I'll upload the gdb output in a minute.
By: callguy (callguy) 2008-04-30 16:27:41
in the interest of saving myself some pain and suffering, i've uploaded the output for the thread that appeared to be related. if you think you need the whole thing let me know and i'll go through the process of cleansing that.
By: sbisker (sbisker) 2008-05-19 13:23:32
I just had this same issue happen on our 1.4.19 asterisk server. My thread iax_thread is very similar, but with more "junk" in it. I'll upload the offending thread's backtrace.
By: Tilghman Lesher (tilghman) 2008-06-03 11:35:45
This is most likely a memory corruption error, and we're going to need you to follow the instructions in doc/valgrind.txt.
By: Tilghman Lesher (tilghman) 2008-06-17 16:14:15
We're going to need the output of valgrind to track this down. There is no other way.
By: Tilghman Lesher (tilghman) 2008-07-14 17:03:44
Closed, due to lack of response. If you're able to provide the requested information, please reopen this issue. If you need assistance, please contact a bug marshal in #asterisk-bugs on Freenode.