[asterisk-bugs] [Asterisk 0011601]: crashes with "*** glibc detected *** corrupted double-linked list" with connections to asterisk manager

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11601 
====================================================================== 
Reported By:                rolek
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11601
Category:                   Core-General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.15  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-19-2007 10:34 CST
Last Modified:              12-24-2007 09:24 CST
====================================================================== 
Summary:                    crashes with "*** glibc detected *** corrupted
double-linked list" with connections to asterisk manager
Description: 
I'm running asterisk 1.4.x with a IAX uplink and some SIP phones.
Essentially, this works fine. However, when making connections to the
asterisk manager interface [from a php application, in a certain timed
fashion], asterisk crashes while showing a notice like:
*** glibc detected *** corrupted double-linked list: 0x081cb7e0 ***
This happens reproducibly on three different boxes, all with different
hardware.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 12-24-07 09:24  
---------------------------------------------------------------------- 
Please report this glibc issue upstream to the Slackware project.  This
should be fixed by them (or further upstream from them, but that is the
correct route). 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-24-07 09:24  Corydon76      Note Added: 0075887                          
======================================================================