[Home]

Summary:ASTERISK-28620: Segfault in chan_pjsip on pj_strcmp when filtering a transmit message
Reporter:Ross Beer (rossbeer)Labels:
Date Opened:2019-11-15 09:14:24.000-0600Date Closed:2021-04-23 11:26:08
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_pjsip
Versions:13.29.1 GIT Frequency of
Occurrence		Occasional
Related
Issues:
Environment:CentOS 7.6Attachments:
Description:Segfault while comparing strings during filtering transmit messages:

{noformat}
Thread 1 (Thread 0x7f52ee277700 (LWP 125559)):
#0  0x00007f560b235594 in pj_strcmp (str1=0x20202020200902c4, str2=0x7f52ee2768c0) at ../include/pj/string_i.h:148
#1  0x00007f560b235775 in pj_strcmp2 (str1=0x20202020200902c4, str2=0x7f540e35c15f "IP4") at ../include/pj/string_i.h:211
       copy2 = {ptr = 0x7f540e35c15f "IP4", slen = 3}
#2  0x00007f540e337ae6 in multihomed_rewrite_sdp (sdp=0x7f551c0694c8) at res_pjsip/pjsip_message_filter.c:151
#3  0x00007f540e3384d8 in filter_on_tx_message (tdata=0x7f52b2b015b8) at res_pjsip/pjsip_message_filter.c:321
       restrictions = 0x0
       prm = {tp_type = PJSIP_TRANSPORT_UDP, tp_sel = 0x0, dst_host = {ptr = 0x7f52b2b01d48 "194.54.8.157", slen = 12}, local_if = 1, ret_addr = {ptr = 0x2f050e8 "185.91.41.30", slen = 12}, ret_port = 5060, ret_tp = 0x2f04f28}
       cseq = 0x7f52ee276a40
       via = 0x7f551c07d5e0
       from = 0x7f52b2b02038
{noformat}
Comments:By: Asterisk Team (asteriskteam) 2019-11-15 09:14:25.145-0600

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

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.
By: Sean Bright (seanbright) 2021-04-23 11:20:24.941-0500

Thank you for the crash report. However, we need more information to investigate the crash. Please provide:

1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1].
2. Specific steps taken that lead to the crash.
3. All configuration information necesary to reproduce the crash.

Thanks!

[1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace


By: Ross Beer (rossbeer) 2021-04-23 11:25:43.754-0500

These were provided to the Digium team via email.

I have not seen this issue for a long time now and we no longer use Asterisk 13.