[asterisk-bugs] [Asterisk 0016806]: segfault in pri_schedule_del at prisched.c:124

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16806 
====================================================================== 
Reported By:                jensvb
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16806
Category:                   Channels/chan_dahdi
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           Older 1.6.0 - please test a newer version 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-11 04:28 CST
Last Modified:              2010-02-17 22:45 CST
====================================================================== 
Summary:                    segfault in pri_schedule_del at prisched.c:124
Description: 
Hi,

I experienced a crash of asterisk 1.6.0.3 in libpri today...

Thanks & Regards
Jens


====================================================================== 

---------------------------------------------------------------------- 
 (0118203) jensvb (reporter) - 2010-02-17 22:45
 https://issues.asterisk.org/view.php?id=16806#c118203 
---------------------------------------------------------------------- 
>> Also, you haven't provided which version of libPRI you're using

asterisk-1.6.0.3
asterisk-addons-1.6.0.1
dahdi-linux-complete-2.1.0.3+2.1.0.2
libpri-1.4.9

(since the crash I put on my cowboy boots and upgraded to the latest
version of everything - if the crash is not glaringly evident in the core
dump then I suggest you close this call) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-17 22:45 jensvb         Note Added: 0118203                          
======================================================================