[asterisk-bugs] [JIRA] (ASTERISK-26373) Crash issue in ast_format_cap_append_from_cap of format_cap.c
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Wed Sep 14 03:57:01 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232274#comment-232274 ]
Asterisk Team commented on ASTERISK-26373:
------------------------------------------
Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.
A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.
Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
> Crash issue in ast_format_cap_append_from_cap of format_cap.c
> -------------------------------------------------------------
>
> Key: ASTERISK-26373
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-26373
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Affects Versions: 13.11.2
> Environment: Virtual Machine on ESXi6 (VM Version 11, 4vCPU, 16Gb RAM), OS: CentOS release 6.8 (Final) x86_84
> Reporter: Denis S.Davydov
>
> Segmentation fault in ast_format_cap_append_from_cap.
> {code}
> Program terminated with signal 11, Segmentation fault.
> #0 0x0000000000526f83 in ast_format_cap_append_from_cap (dst=0x7fa731384ab0, src=0x7fa6d5098350, type=AST_MEDIA_TYPE_UNKNOWN) at format_cap.c:308
> 308 struct format_cap_framed *framed = AST_VECTOR_GET(&src->preference_order, idx);
> #0 0x0000000000526f83 in ast_format_cap_append_from_cap (dst=0x7fa731384ab0, src=0x7fa6d5098350, type=AST_MEDIA_TYPE_UNKNOWN) at format_cap.c:308
> __idx = 0
> framed = 0x7fa6d512f190
> idx = 0
> res = 0
> #1 0x00000000004c2e53 in ast_request (type=0x7fa6e1854580 "SIP", request_cap=0x7fa6d5098350, assignedids=0x0, requestor=0x7fa6d54b3068, addr=0x7fa6e1854584 "3112", cause=0x7fa6e1854680) at channel.c:6068
> tmp_cap = 0x7fa7313bf700
> tmp_fmt = 0xbc67d0
> best_audio_fmt = 0xbc67d0
> joint_cap = 0x7fa731384ab0
> chan = 0x17a62c0
> c = 0x7fa6e1855fc0
> res = 0
> foo = 32679
> __PRETTY_FUNCTION__ = "ast_request"
> {code}
> backtrace.txt and full.txt are in attachment.
> I can give you configuration snippet by your request. Compiled flags on my Asterisk-PBX is DONT_OPTIMIZE, COMPILE_DOUBLE, LOADABLE_MODULES, BETTER_BACKTRACES, MALLOC_DEBUG, BULD_NATIVE. Mmlog useless, there's nothing.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list