[asterisk-bugs] [JIRA] (ASTERISK-29196) res_pjsip: Segmentation fault in pj_strdup

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29196:
------------------------------------------

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> res_pjsip: Segmentation fault in pj_strdup
> ------------------------------------------
>
>                 Key: ASTERISK-29196
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29196
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 18.1.0
>            Reporter: Mauri de Souza Meneguzzo (3CPlus)
>
> Asterisk instances running 18.1.0 are crashing with segmentation fault, nothing is shown in the logs besides the segfault.
> After we upgraded to 18.1.0 this issue is happening multiple times a day, going back to 18.0.1 fixed the issue.
> {noformat}
> #0  0x00007fb40787f5bd in pj_strdup (pool=0x7fb37453c490, dst=0x7fb378140b18, src=0x0) at ../include/pj/string_i.h:40
> #1  0x00007fb40782806c in pjmedia_sdp_neg_modify_local_offer2 (pool=0x7fb37453c490, neg=0x7fb3682f0f30, flags=1, local=0x7fb3680d1fb8)
>     at ../src/pjmedia/sdp_neg.c:336
> #2  0x00007fb4077a1d9e in inv_check_sdp_in_incoming_msg (inv=0x7fb3682f0c68, tsx=0x7fb3a8154208, rdata=0x7fb38832d3b8)
>     at ../src/pjsip-ua/sip_inv.c:2084
> #3  0x00007fb4077a5bbd in inv_on_state_early (inv=0x7fb3682f0c68, e=0x7fb2f4ad7a70) at ../src/pjsip-ua/sip_inv.c:4447
> #4  0x00007fb40779f4a3 in mod_inv_on_tsx_state (tsx=0x7fb3a8154208, e=0x7fb2f4ad7a70) at ../src/pjsip-ua/sip_inv.c:736
> #5  0x00007fb4077ec047 in pjsip_dlg_on_tsx_state (dlg=0x7fb3960c48a8, tsx=0x7fb3a8154208, e=0x7fb2f4ad7a70) at ../src/pjsip/sip_dialog.c:2129
> #6  0x00007fb4077ec8b9 in mod_ua_on_tsx_state (tsx=0x7fb3a8154208, e=0x7fb2f4ad7a70) at ../src/pjsip/sip_ua_layer.c:178
> #7  0x00007fb4077e499a in tsx_set_state (tsx=0x7fb3a8154208, state=PJSIP_TSX_STATE_PROCEEDING, event_src_type=PJSIP_EVENT_RX_MSG,
>     event_src=0x7fb38832d3b8, flag=0) at ../src/pjsip/sip_transaction.c:1272
> #8  0x00007fb4077e75a6 in tsx_on_state_proceeding_uac (tsx=0x7fb3a8154208, event=0x7fb2f4ad7b60) at ../src/pjsip/sip_transaction.c:2975
> #9  0x00007fb4077e58fe in pjsip_tsx_recv_msg (tsx=0x7fb3a8154208, rdata=0x7fb38832d3b8) at ../src/pjsip/sip_transaction.c:1832
> #10 0x00007fb4077e3ec1 in mod_tsx_layer_on_rx_response (rdata=0x7fb38832d3b8) at ../src/pjsip/sip_transaction.c:893
> #11 0x00007fb4077c8d4d in pjsip_endpt_process_rx_data (endpt=0x55dc325f63b8, rdata=0x7fb38832d3b8, p=0x7fb3a5c32b00 <param>,
>     p_handled=0x7fb2f4ad7c94) at ../src/pjsip/sip_endpoint.c:938
> #12 0x00007fb3a5c00b33 in distribute (data=0x7fb38832d3b8) at res_pjsip/pjsip_distributor.c:955
> #13 0x000055dc3006a364 in ast_taskprocessor_execute (tps=0x7fb368140060) at taskprocessor.c:1237
> #14 0x000055dc30074160 in execute_tasks (data=0x7fb368140060) at threadpool.c:1354
> #15 0x000055dc3006a364 in ast_taskprocessor_execute (tps=0x55dc325f42e0) at taskprocessor.c:1237
> #16 0x000055dc30071d61 in threadpool_execute (pool=0x55dc325f2ce0) at threadpool.c:367
> #17 0x000055dc3007399b in worker_active (worker=0x7fb3780444d0) at threadpool.c:1137
> #18 0x000055dc3007370a in worker_start (arg=0x7fb3780444d0) at threadpool.c:1056
> #19 0x000055dc3007d486 in dummy_start (data=0x7fb3f41c4e90) at utils.c:1299
> {noformat}



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