[asterisk-dev] Call and seg fault

Dennis Buteyn dennis.buteyn at xorcom.com
Sun Jan 24 02:26:54 CST 2021


On 1/24/21 10:19 AM, LSV wrote:
> What I should do?
>
> пт, 22 янв. 2021 г. в 21:15, Joshua C. Colp <jcolp at digium.com 
> <mailto:jcolp at digium.com>>:
>
>     On Fri, Jan 22, 2021 at 7:13 AM Killian Matter
>     <matter.killian at gmail.com <mailto:matter.killian at gmail.com>> wrote:
>
>         Well hello, when the call is up, working,  then asterisk put
>         up a seg fault error. Just Segmentation Fault.
>         What info would you want/do you need to help
>         ?
>
>
>     A backtrace is required for crashes[1]. If this is regarding your
>     custom code then you'd likely need to actually show the code or
>     provide deeper understanding of what is going on. Personally I
>     don't look at unlicensed code, but others may choose to.
>
>     [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
>
>
>     -- 
>     Joshua C. Colp
>     Asterisk Technical Lead
>     Sangoma Technologies
>     Check us out at www.sangoma.com <http://www.sangoma.com/> and
>     www.asterisk.org <http://www.asterisk.org/>
>     -- 
>     _____________________________________________________________________
>     -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
>     asterisk-dev mailing list
>     To UNSUBSCRIBE or update options visit:
>     http://lists.digium.com/mailman/listinfo/asterisk-dev
>
I'd start with loading the coredump into gdb.

Josh already linked the official Asterisk docs but in addition, a pretty 
decent example of how to analyze a coredump wtih gdb can be found here: 
http://www.brendangregg.com/blog/2016-08-09/gdb-example-ncurses.html

Dennis Buteyn
Xorcom Ltd


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20210124/a281156b/attachment-0001.html>


More information about the asterisk-dev mailing list