[asterisk-bugs] [JIRA] (ASTERISK-26307) Crash from res_pjsip_caller_id.c

Bill Brigden (JIRA) noreply at issues.asterisk.org
Tue Aug 30 07:45:01 CDT 2016


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

Bill Brigden commented on ASTERISK-26307:
-----------------------------------------

I've sent you logs from the most recently crash.

I also saw a report here - ASTERISK-25942 - which references a similar (but non crashing scenario) where a SIP update  / re-invite needs to determine values to set? Not sure if related..

> Crash from res_pjsip_caller_id.c
> --------------------------------
>
>                 Key: ASTERISK-26307
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26307
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_caller_id
>    Affects Versions: 13.10.0
>         Environment: Linux xx 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64 GNU/Linux
>            Reporter: Bill Brigden
>            Assignee: Bill Brigden
>         Attachments: bt-220816.txt, bt-full.txt
>
>
> I've had a couple of random crashes, shown in syslog as:
> {quote}
> Aug 19 11:50:04 pbx-02 kernel: [22213515.179507] asterisk[15754]: segfault at 40 ip 00007ff54b0b367a sp 00007ff55bffe820 error 4 in res_pjsip_caller_id.so[7ff54b0b2000+3000]
> {quote}
> Will attach BT (both normal and full). Oddly, I have compiled with: DONT_OPTIMIZE, DEBUG_THREADS, BETTER_BACKTRACES however it shows that some values are optimized out.



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



More information about the asterisk-bugs mailing list