[asterisk-bugs] [JIRA] (ASTERISK-27170) segfault in pj_sockaddr_in_set_str_addr

[nappsoft (JIRA)]

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

nappsoft commented on ASTERISK-27170:
-------------------------------------

Yeah, I did. But we had the same issues with the bundled version in the past. Currently we use pjproject trunk with the same config_site.h and configure flags as you are using in the bundled version so I do not understand why the bundled version should be supported why an identically compiled version is not. 

As the crashes (with external pjsip) always happened at the same point in the library independent of the version we were using I doubt that this is a pjproject issue. But well, close this bug like all the crash reports from users during the last 3 weeks (there are several reports of crashes in the bug tracker, all ended with "waiting for feedback"). If you take the time and read through the last four issues I've reported during the last 12 months you will see that I only report issues that are issues and usually in a way (with quite some pre-analysis) that makes fixing the issue easy. During the same time I've also reported some issues to the pjproject (including patches).

But well. I can keep these things for me in the future if you prefer.

> segfault in pj_sockaddr_in_set_str_addr
> ---------------------------------------
>
>                 Key: ASTERISK-27170
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27170
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/General
>    Affects Versions: 13.16.0
>         Environment: 64bit linux musl 1.1.15
>            Reporter: nappsoft
>            Assignee: Unassigned
>
> From time to time asterisk crashes in pj_sockaddr_i_set_str_add. The asterisk version we use is 13.16.0 with some stability patches that flew into 13.17.0 (we will update to 13.17.0 soon). But we already had the same crashes with unpatched 13.16.0 versions and with older versions as well.
> According to the sip traces the last thing that happened was a sip transfer. The messageflow was:
> REFER (Phone) -> 202 Accepted (PBX) -> NOTIFY Trying (PBX) -> NOTIFY OK (PBX) -> BYE (Phone) - > OK (PBX for the BYE message) -> OK (Phone for the NOTIFY Trying) -> OK (Phone for the NOTIFY OK)
> As these are embedded systems with limited resources it's always difficult to make crash dumps there or to run asterisk in gdb... I'll try to get some complete backtraces in the future, but maybe somebody has an idea based on the described scenario. => maybe there is a race condition when the Phone sends OK messages for the NOTIFY messages after that the phone has already sent a BYE for the same call?



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