[asterisk-bugs] [Asterisk 0011174]: Crash related to ast_module_user_remove

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11174 
====================================================================== 
Reported By:                lvl
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11174
Category:                   Core-General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 89046 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             11-06-2007 15:04 CST
Last Modified:              11-07-2007 15:04 CST
====================================================================== 
Summary:                    Crash related to ast_module_user_remove
Description: 
Asterisk randomly crashes after this sequence of events:

== Manager 'call' logged on from 127.0.0.1
-- Executing [s at callee:3] Hangup("Local/s at callee-c93d,2", "") in new
stack
== Spawn extension (callee, s, 3) exited non-zero on
'Local/s at callee-c93d,2'
*** glibc detected *** asterisk: free(): invalid pointer: 0x081b8f79 ***

======= Backtrace: =========
/lib/i686/cmov/libc.so.6[0xb7de9cf5]
/lib/i686/cmov/libc.so.6(cfree+0x90)[0b7ded790]
asterisk(__ast_module_user_remove+0x11c)[0x80b7cf0]
/usr/lib/asterisk/modules/chan_local.so[0xb6f247df]
asterisk(ast_hangup+0x372)[0x8085854]
asterisk[0x80cf76f]
asterisk[0x80cf9bf]
asterisk[0x8110eee]
/lib/i686/cmov/libpthread.so.0[0xb7f3646b]
/lib/i686/cmov/libc.so.6(clone+0x5e)[0xb7e534de]
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 11-07-07 15:04  
---------------------------------------------------------------------- 
Again, for these types of problems, the backtrace is unlikely to show us
the problem.  It is the messages that valgrind and the MALLOC_DEBUG options
show us that will be helpful.

Specifically, the problem is that by the time Asterisk crashes with a
memory corruption error, the memory corruption happened well before the
crash.  The crash is just the result of finding corrupt memory. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-07-07 15:04  Corydon76      Note Added: 0073324                          
======================================================================