[asterisk-dev] Serious Asterisk 13.10.0 issue
Ross Beer
ross.beer at outlook.com
Fri Jun 24 08:34:15 CDT 2016
Ok,
I believe the segfault to be related to a previous issue:
https://issues.asterisk.org/jira/browse/ASTERISK-26099
This issue has been resolved, however looking at the 'configure' script it looks like it isn't finding the PJPROJECT method. Should there be a variable used when compiling PJPROJECT or is this automatically discovered?
Regards,
Ross
________________________________
From: asterisk-dev-bounces at lists.digium.com <asterisk-dev-bounces at lists.digium.com> on behalf of Ross Beer <ross.beer at outlook.com>
Sent: 24 June 2016 13:41
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] Serious Asterisk 13.10.0 issue
The following issue has been created for the seg fault:
https://issues.asterisk.org/jira/browse/ASTERISK-26147
________________________________
From: asterisk-dev-bounces at lists.digium.com <asterisk-dev-bounces at lists.digium.com> on behalf of Joshua Colp <jcolp at digium.com>
Sent: 24 June 2016 13:20
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] Serious Asterisk 13.10.0 issue
Ross Beer wrote:
> Hi,
>
>
> Also just had the following crash:
>
>
> [Thread debugging using libthread_db enabled]
>
> Using host libthread_db library "/lib64/libthread_db.so.1".
>
> Core was generated by `/usr/sbin/asterisk -f -vvvg -c'.
>
> Program terminated with signal SIGSEGV, Segmentation fault.
>
> #0 0x00007f4e7c16fb29 in pj_atomic_dec_and_get () from /lib64/libpj.so.2
>
> [Current thread is 1 (Thread 0x7f4e6d9fc700 (LWP 10799))]
>
> #0 0x00007f4e7c16fb29 in pj_atomic_dec_and_get () at /lib64/libpj.so.2
>
> #1 0x00007f4e7dcbab30 in pjsip_tx_data_dec_ref () at
> /lib64/libpjsip.so.2
>
> #2 0x00007f4e7dcc5f07 in tsx_shutdown () at /lib64/libpjsip.so.2
>
> #3 0x00007f4e7dcc6141 in tsx_set_state () at /lib64/libpjsip.so.2
>
> #4 0x00007f4e7dcc61ca in tsx_on_state_terminated () at
> /lib64/libpjsip.so.2
>
> #5 0x00007f4e7dcc6227 in tsx_timer_callback () at /lib64/libpjsip.so.2
>
> #6 0x00007f4e7c17e3b7 in pj_timer_heap_poll () at /lib64/libpj.so.2
>
> #7 0x00007f4e7dcb5c3b in pjsip_endpt_handle_events2 () at
> /lib64/libpjsip.so.2
>
> #8 0x00007f4e6fbac508 in monitor_thread_exec (endpt=<optimized out>)
> at res_pjsip.c:3863
>
> delay = {sec = 0, msec = 10}
>
> #9 0x00007f4e7c16fa56 in thread_main () at /lib64/libpj.so.2
>
> #10 0x00007f4ec5ce261a in start_thread () at /lib64/libpthread.so.0
>
> #11 0x00007f4ec501e59d in clone () at /lib64/libc.so.6
>
>
> Should this be raised as a bug?
Yes.
--
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com<http://www.digium.com> & www.asterisk.org<http://www.asterisk.org>
[https://www.digium.com/sites/digium/themes/digium/logo.png]<http://www.digium.com/>
Business Phone Systems | Unified Communications | Digium<http://www.digium.com/>
www.digium.com
Digium offers full Unified Communications solutions with on-premises and hosted business phone systems, IP phones, and Asterisk hardware.
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20160624/27b9a8e6/attachment-0001.html>
More information about the asterisk-dev
mailing list