[asterisk-bugs] [JIRA] (ASTERISK-28086) Segfault in ast_senddigit_end using PJSIP

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-28086:
--------------------------------------------

Your backtraces have no symbols and are not usable.  You need to run asterisk that does not have the symbols stripped from it.

You can use the {{file}} command to determine if you have symbols:
{noformat}
rmudgett at piglet:~/projects/asterisk/ws1/v16 (v16)$ file /usr/sbin/asterisk
/usr/sbin/asterisk: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=84c7982bc02ad1d00a7e38fa03e6473ece79e0c4, not stripped

rmudgett at piglet:~/projects/asterisk/ws1/v16 (v16)$ file /usr/lib/asterisk/modules/res_pjsip.so
/usr/lib/asterisk/modules/res_pjsip.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=227cd8a844382f758f54eeccb450dc0330cded44, not stripped
{noformat}
If your modules are {{not stripped}} you have symbols available and backtraces will be usable.

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

> Segfault in ast_senddigit_end using PJSIP
> -----------------------------------------
>
>                 Key: ASTERISK-28086
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28086
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip, Resources/res_pjsip_session
>    Affects Versions: 13.19.0
>         Environment: Gentoo (physical), Debian (AWS)
>            Reporter: Jeremiah Gadd
>            Assignee: Jeremiah Gadd
>              Labels: pjsip
>         Attachments: core-20180926-094817-brief.txt, core-20180926-094817-full.txt, core-20180926-094817-locks.txt, core-20180926-094817-thread1.txt
>
>
> It appears there may be a race condition in which PJSIP attempts to end the sending of a DTMF tone after a bridge is destroyed, causing PJSIP to try to send to a non-existent channel.
> I've attached the corresponding core dumps.
> Thread 1 (Thread 0x7f45562ef700 (LWP 3781)):
> #0  0x00007f49d9b49233 in ?? () from /usr/lib64/asterisk/modules/chan_pjsip.so
> #1  0x00000000004b5fe7 in ast_senddigit_end ()
> #2  0x00007f49da56d29c in ?? () from /usr/lib64/asterisk/modules/app_senddtmf.so
> #3  0x000000000054ce1e in ?? ()
> #4  0x000000000054fbaa in ?? ()
> #5  0x00000000005dd2dd in ?? ()
> #6  0x00000000005eb91a in ?? ()
> #7  0x00007f4a6a065f3a in __pthread_mutex_unlock_full () from /lib64/libpthread.so.0
> #8  0xb5e6219ff3277d21 in ?? ()
> #9  0x0000000000000000 in ?? ()



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