[asterisk-dev] Segfaults with 1.4.0 and E1s

[Matthew Fredrickson]

Can you post a detailed bug report on bugs.digium.com as well as a 
complete backtrace?  My first thought is that the id value is very 
wrong.  In fact, it shouldn't even get to this line of code with the 
current version of libpri since the id is a negative value.  Are you 
sure you updated libpri and zaptel as well as asterisk when you updated 
to 1.4?

Matthew Fredrickson

On Dec 30, 2006, at 3:45 PM, Gavin Hamill wrote:

> Hi :) We've been running 1.4.0 for a couple of days and have had a 
> segfault
> each day.
>
> Ultimately the crash is the result of the same thing:
>
> #0  0x00002aaaae2c61c8 in pri_schedule_del (pri=0x108d9f0, 
> id=-553648128) at
> prisched.c:118
> 118          pri->pri_sched[id].callback = NULL;
>
> but in each, case the workload of the system was dramatically 
> different:
>
> Complex agent setup with dozens of queues and SIP handsets
> http://pastebin.ca/296966
>
> Simplistic setup passing all calls through to legacy PBX.
> http://pastebin.ca/297141
>
> If this is the wrong forum for this report, please let me know so I 
> can update
> http://www.voip-info.org/tiki-index.php?page=Asterisk%20debugging
>
> Cheers,
> Gavin.
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev