Summary:ASTERISK-10353: Segfaults on dial_exec_full()
Reporter:Faidon Liambotis (paravoid)Labels:
Date Opened:2007-09-20 23:29:29Date Closed:2011-06-07 14:00:55
Versions:Frequency of
Environment:Attachments:( 0) bt.txt
( 1) bt-full.txt
( 2) thread-bt.txt
Description:A user reported on the Debian bug tracking system (http://bugs.debian.org/438702) a segfault when he unsuccessfully tried to call from his SIP softphone to a Zap channel.

We've managed to get a core dump and get a proper backtrace from it.


The user also provided verbose/debug enabled log files and are available if requested.
Comments:By: Dmitry Andrianov (dimas) 2007-09-28 01:17:35

To me, crash in malloc/free related calls is usually a sign of some memory corruption. Memory could be corrupt by completely different thread so stacktrace of crashed thread won't help. If you can reproduce the problem, I would suggest running asterisk under valgrind - it will quickly catch problems with memory manipulation.

Btw, have you turned DONT_OPTIMIZE on? And do you run unmodified version of app_dial.c ? I can not see in the code a place where dial_exec_full directly calls ast_frame_free or ast_frfree as it is in your stacktrace...

By: Jason Parker (jparker) 2007-10-26 14:48:56

Closing, due to no response in a month.  Please reopen if you are able to answer the questions dimas asked.