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

[George Joseph (JIRA)]

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

George Joseph commented on ASTERISK-27170:
------------------------------------------

The difference is that we don't know what's in pjproject trunk that we don't have in bundled.  We'd be just guessing at what trunk was at the time you compiled vs what it is when we troubleshoot.  Maybe someone committed something in trunk that doesn't work for us.  It's happened before.  That's why we created bundled and why we're starting to get strict about using bundled if you want support.   If there's a specific pjproject commit that's in trunk that you think _needs_ to be in bundled, just let us know.  

We don't have to close the issue but there's nothing in _this_ issue to troubleshoot.   No logs or backtraces.   I'll give you a pass on bundled but you must compile asterisk with DONT_OPTIMIZE and BETTER_BACKTRACES and compile pjproject with its symbols left intact, the provide a backtrace.  Failing that, a scenario we can reproduce would be fine.  Otherwise we got nuthin. :)



> 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)