[asterisk-bugs] [JIRA] (ASTERISK-26868) ARI: Asterisk crash - frame copy into invalid memory during bridging operations

[Marin Odrljin (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235923#comment-235923 ] 

Marin Odrljin commented on ASTERISK-26868:
------------------------------------------

I have core files. I'm not sure what else I have to execute before, but when I do it in following order:

# gdb -se "asterisk" -ex "bt full" -ex "thread apply all bt" --batch -c core > /tmp/backtrace.txt
# gdb -se "asterisk" -c core | tee /tmp/backtrace.txt
set logging on
(gdb) f 0
(gdb) p control->bridge

I get following:

For backtrace 20170317_backtrace.txt:
(gdb) p 0
$1 = 0
(gdb) p control->bridge
No symbol "control" in current context.

For backtrace 20170317_2_backtrace.txt:
(gdb) p 0
$1 = 0
(gdb) p control->bridge
$2 = (struct ast_bridge *) 0x632e6c6f72746e6f

Let me know if I have to do anything else differently before this. Also, I can send you core files if you like and then you can do whatever you want.

> ARI: Asterisk crash - frame copy into invalid memory during bridging operations
> -------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26868
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26868
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Bridges/bridge_simple, Resources/res_ari_bridges, Resources/res_stasis
>    Affects Versions: 13.11.2, 14.2.1
>         Environment: Debian 8
>            Reporter: Marin Odrljin
>            Assignee: Unassigned
>         Attachments: 20170317_2_backtrace.txt, 20170317_2_debug_log_crash.txt, 20170317_2_var-log-messages.txt, 20170317_backtrace.txt, 20170317_debug_log.txt, 20170317_var-log-messages.txt, backtrace.txt, cli_log - simulation.txt, debug_log - simulation.log, java_app_log.txt
>
>
> Asterisk occasionally crashes while adding channel to bridge with ARI. I'm not sure if this is because of ARI or not, and also not 100% sure if the real problem is adding channel to bridge, but I think so. This happens in one of thousands of calls so it is not so obvious and easy to reproduce. But I got segfault several times in last few months on both asterisk 13.11.2 and 14.2.1.
> I have analyzed my app's log and it looks like every time it happened after the same two actions: 1. enter bridge, 2. answer call. Currently I'm mostly working on my routing app which receives IN call, finds route for OUT call, dials it and joins them together in bridge. So basically the flow of the call is always the same:
> -	IN call comes to asterisk Stasis app
> -	App sends Ring to IN call (channel)
> -	Create bridge
> -	Add IN call (channel) to bridge
> -	Dial on OUT call
> -	Add OUT call (channel) to bridge (after it is answered)
> -	Answer IN call
> Crash always happens on last two steps: add OUT call to bridge and answer IN call.
> Finally, after 1-2 months I managed to catch core dump so I'm attaching backtrace file.



--
This message was sent by Atlassian JIRA
(v6.2#6252)